Replies: 1 comment
-
I think this is just this issue here: #9936 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have two laptops and I kept one of them using cgroups v1 to be able to still use docker for some work related tasks (mainly docker-compose). My other laptop is cgroupsv2 and podman only. Both of them are running archlinux and are updated regularly.
Now after one of the last updates systemd got updated on my work laptop and this resulted in cgroupsv2 being mounted by default. This shouldn't be a problem, since docker now also supports this and therefore there is no reason to stick on v1.
The problem is that podman just stopped working properly on that laptop while its running fine on my other laptop (which is on the same kernel/systemd/podman versions, also the same root filesystem which is ext4) I really can't spot any differences.
The problem occurs when I pull a bigger image like ubuntu, golang or rust images. It works fine with alpine or debian though.
I searched for the error and found some older issues that hinted me at using cgroupfs as cgroup manager, but this also doesn't help. Increasing the log-level also doesn't show any meaningfull hints. I cleaned my ~/.local/share/containers completely, reinstalled podman, tried using the latest master version (yesterday), using runc instead of crun, but all to no success.
Here is the
podman info
of the broken machine, I really hope someone might have another idea. I'd really like to avoid just freshly setting up the laptop.Pulling as root works like expected...
I would really appreciate any hints, thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions