-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
podman stats not working, returns cgroup deleted #9252
Comments
Could you try this on the main branch or podman 3.0. We have made some changes to allow stats to work on systems that do not enable all of the cgroups stats attempts to read. |
I believe it is fixed in main branch and 3.0. Reopen if I am mistaken. |
Just upgrade and installed Podman 3.0.0 on Ubuntu 20.04.2 LTS. Ran into these two issues during upgrade: After upgraded to Podman 3.0, still can reproduce with steps above. kiritow@ubuntu-podman:~$ sudo podman stats
Error: unable to load cgroup at /machine.slice/machine-libpod_pod_4f8e36a5b9cc577a1b81592496579396e503d8126205bfa233ed26d651dce944.slice/libpod-3a5d6b2a4ffcb29587ddfb5f5edf7fc7a9ba51e0755d796b81b589ceab858d83.scope/init.scope: cgroup deleted (I'm upgrading and running this command on another virtual machine, because I can't stop the original server now) Sorry @rhatdan but I can't reopen this issue. There's no 'reopen' button. Output of
Output of
Package info (e.g. output of
Additional environment details (AWS, VirtualBox, physical, etc.): |
I've found a workaround, Ubuntu Server 20.04 LTS uses cgroup V1 by default. Add |
@giuseppe Ideas? |
can you show me the output for the following command (where
|
podman run -itd ubuntu-cn
podman run -d mcsm-mc-base
|
After reading source code [pkg/cgroups/cgroups.go], [libpod/stats.go], [libpod/container.go], now I've found that [pkg/cgroups/cgroups.go:334] will stat the following directories:
I've manually checked them all, only the
From [libpod/container.go:957] and #8397 I get
|
thanks! PR here: #9464 |
do not raise an error if the cgroup exists at least on one controller. Previously it expected the cgroup to exists under all the controllers. [NO TESTS NEEDED] Closes: containers#9252 Signed-off-by: Giuseppe Scrivano <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman stats
not working. Usingroot
,podman stats
returnsError: unable to load cgroup at /machine.slice/machine-libpod_pod_8cbc0cae539eb254c64e9fb5a613b151ed364c351083af55f5437fa4661e217f.slice/libpod-3b221f7e8b39f1e85111d88e7e8e864f7acbca8a6b880504cbd34793a72e8997.scope/init.scope: cgroup deleted
Steps to reproduce the issue:
Reboot the machine, and login as root
Start all pods
podman stats
fails.Describe the results you received:
podman stats
returnsError: unable to load cgroup at /machine.slice/machine-libpod_pod_8cbc0cae539eb254c64e9fb5a613b151ed364c351083af55f5437fa4661e217f.slice/libpod-3b221f7e8b39f1e85111d88e7e8e864f7acbca8a6b880504cbd34793a72e8997.scope/init.scope: cgroup deleted
Describe the results you expected:
podman stats
should work fine.Additional information you deem important (e.g. issue happens only occasionally):
docker
is not installed on this machine.podman ps -a
:podman pod ls
uname -a
lsb_release -a
Output of
podman version
:podman version
is2.2.1
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
Additional environment details (AWS, VirtualBox, physical, etc.):
Virtualized with VMWare Workstation 16.
The text was updated successfully, but these errors were encountered: