-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 top: read /proc/226420/cmdline: no such process #22619
Comments
Actually I think this is a real error and if one tries it will be not to hard to build a reproducer for as this reminds me off #22103 (comment) which shows that checking only ENOENT is not enough when we parse That however does not explain why we have process in such a state here in the test as we only run |
the kernel returns ESRCH if the process terminates between the |
agreed, me neither my only thought is that top got killed by a signal in the meantime or alternatively that another process entered the cgroup (looks like psgo collects the pids for all processes based on the cgroup) then exited/got killed If it is the first one the test will still fail as top would return no results |
I've opened a PR for psgo: containers/psgo#155 |
A friendly reminder that this issue had no activity for 30 days. |
Weird one-off seen in debian rootless:
I fully expect this one to languish, then get closed in a month or two.
The text was updated successfully, but these errors were encountered: