-
-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] k3s refuses to start with rootless Podman #1120
Comments
This solution helped me here: |
Hello! I'm facing the same issue on Oracle Linux 8 with CGroupsV2 and rootless podman. I'm already using CGroupsV2 so no additional changes have been required. But still the cluster was unable to spin-up. The command above—especially the But unfortunately it is not sufficient. The cluster starts up but is unable to launch any pod. The log file is full of entries like this:
I have been facing the same issue with KinD (kubernetes-sigs/kind#3234) and @aojea with @AkihiroSuda traced it back [1], [2] to Hope this helps. |
The upstream runc PR has just been merged. When that's available in a release, it could potentially help here. Now that is merged, it may also work out of the box without |
The upstream runc PR has been labeled 1.2.0 just now, so we can hopefully expect a release in the following weeks (months?). From that point on what's a reasonable time expectation to get a resolution in k3s? Thanks |
Still needed for non-filesystem stuffs such as sysctl
Likely to take at least a month |
I can verify, that the podman version 4.3.1 |
What did you do
k3d cluster create
What did you expect to happen
The cluster should be created successfully.
Screenshots or terminal output
The k3s container kept bootlooping.
Which OS & Architecture
Which version of
k3d
Which version of docker
The text was updated successfully, but these errors were encountered: