You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environmental Info:
K3s Version:
k3s version v1.32.0+k3s1 (cca8fac)
go version go1.23.3
Node(s) CPU architecture, OS, and Version:
Linux ubuntu 6.8.0-55-generic #57-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 12 23:42:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
1 master
Describe the bug:
Starting the k3s-rootless service results in the message "failed to start the child: fork/exec /proc/self/exe: operation not permitted"
Steps To Reproduce:
Installed K3s: as root user, executed "curl -sfL https://get.k3s.io | sh - > master_setup.log"
Enabled lingering and delegation for the user
Downloaded the file k3s-rootless.service to user systemd/user folder
reload the systemd daemon, and started the service
Expected behavior:
k3s gets started running as an unprivileged user
Actual behavior:
k3s refuses to start
Additional context / logs:
The text was updated successfully, but these errors were encountered:
I am unable to reproduce this. Rootless is also working correctly in our CI tests.
I suspect you have selinux or some other security module in place. Check the audit logs and figure out what is preventing this process from forking/re-execing.
Environmental Info:
K3s Version:
k3s version v1.32.0+k3s1 (cca8fac)
go version go1.23.3
Node(s) CPU architecture, OS, and Version:
Linux ubuntu 6.8.0-55-generic #57-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 12 23:42:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
1 master
Describe the bug:
Starting the k3s-rootless service results in the message "failed to start the child: fork/exec /proc/self/exe: operation not permitted"
Steps To Reproduce:
Expected behavior:
k3s gets started running as an unprivileged user
Actual behavior:
k3s refuses to start
Additional context / logs:
The text was updated successfully, but these errors were encountered: