On 7/12/24 09:13, Dirk Försterling via Podman wrote:
Hello all,
I see the message 'invalid internal status, try resetting the pause process with
"podman system migrate": could not find any running process: no such
process' quite often upon executing podman (rootless).
In the net I could only find that this can happen after a host reboot. But in my case
there is no reboot, so I am curious wich conditions actually have to be met for this
message to appear. Yes, after "podman system migrate", I can use podman again,
but it might occur just a minute later, or a day. The only observation I had besides the
error message is, that after that "podman system migrate" I still see a couple
of containers in state "Stopping". With those, podman rm -f always complains
that it cannot kill the proces, but at least it can remove the containers.
I'm curious if I could prevent that "invalid internal status" completely
(because it disturbs my automation), but then I would need somebody explaining to me why
this does actually happen. Any hints?
-dirk
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
podman system migrate recreates the default rootless user's user
namespace. This looks like something is collapsing for some reason.
Changing of /etc/subuid and /etc/subgid can require a system migrate.
What version of Podman are you using? Output of podman info would be
helpful. Usually questions like this are best handled within a github
issue.