Oracle Linux 9 Installation Failure

[MaximVasin]

Environmental Info:
K3s Version:
v1.23.8+k3s1

Node(s) CPU architecture, OS, and Version:
Linux ol9.mshome.net 5.15.0-0.30.19.el9uek.x86_64 #2 SMP Wed Jun 15 22:59:49 PDT 2022 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:
Single node installation

Describe the bug:
K3s does not install

Steps To Reproduce:
curl -sfL https://get.k3s.io | sh -

Expected behavior:
k3s is installed

Actual behavior:
Installation script fails during installation of k3s-selinux package with:

Problem opening package k3s-selinux-1.1-1.el8.noarch.rpm
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

Additional context / logs:

Backporting

• Needs backporting to older releases

[brandond]

Duplicate of #5588 - can you try with curl -sfL https://get.k3s.io | INSTALL_K3S_CHANNEL=latest sh -

[MaximVasin]

k3s installs but fails to start due some selinux issues, please see the log from journalctl in k3s.log attached
k3s.log

[brandond]

Jul 07 21:54:06 ol9.mshome.net k3s[1998]: time="2022-07-07T21:54:06+04:00" level=fatal msg="extracting data: open /var/lib/rancher/k3s/data/f4431393712ffbc38bd97607e1f813faef14e378c15e53ea07e11c6bbe9a634f-tmp/bin/containerd-shim-runc-v2: permission denied"

Did you get the k3s-selinux package installed successfully? It looks like selinux is denying some very basic startup operations.

[MaximVasin]

yes, k3s-selinux package is installed

[max@ol9 ~]$ rpm -qa | grep k3s
k3s-selinux-1.2-1.el8.noarch

[brandond]

You might just run k3s-uninstall.sh and then reinstall now that you've got the selinux package installed. That's probably easier than trying to manually relabel everything with chcon.

[stale]

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.