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
rootless podman stopped working after upgrading from 1.9.4 to 2.0.6 #7650
Comments
So, I'm unable to reproduce this locally on debian 10, but couple of pointers from @mheon: Either:
OR |
@lsm5 yes i'm using "su - $user" - but i did the same while using 1.9.4 - i can also downgrade to 1.9.4 and it immediately starts to work again. |
@mheon was this ever supposed to work and we broke it recently? @disaster123 i'm in the process of building 2.1.0, I suggest you give that a try once it's ready as well. |
I'm astonished this ever worked, honestly. I guess that it was using cgroupfs by default on v1.9.x and v2.0.x is (correctly) defaulting to systemd cgroups for cgroupsv2. You can try I strongly suspect your systemd user session isn't running, which would be the better fix as it would actually allow cgroup delegation for the containers. |
@disaster123 do you have the dbus-user-session package installed in your debian? |
yes |
Same problem with v2.1.0 and even with ssh to user and running user session. (Error: sd-bus call: Permission denied: OCI runtime permission denied error) - i think this is related to old systemd => #6368) |
if you think its because of old systemd, can you try installing a newer one from buster-backports? I am using Debian 10 with cgroupv2 and systemd as the cgroup manager for podman. also here is a full list of packages installed on my system. this is a minimal install so it may help in tracking down what package maybe missing. |
Also try (as root): |
A friendly reminder that this issue had no activity for 30 days. |
no answer whether the default or fall back has changed |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
After upgrading from 1.9.4 to 2.0.6 i'm not able to run a container.
Steps to reproduce the issue:
install podman 2.0.6~2 under debian buster
run podman
Describe the results you received:
Describe the results you expected:
Container should start.
Additional information you deem important (e.g. issue happens only occasionally):
debug log level
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
The text was updated successfully, but these errors were encountered: