"container state improper" in Rootless Containers/Pod After Reboot #10036
Replies: 7 comments 14 replies
-
Is your |
Beta Was this translation helpful? Give feedback.
-
Aaaaand the issue just went away on its own... I was attempting to use "backups(?)" created before these issues with podman export, by creating a new pod, new network, and importing the exports as images and then deploying containers. For giggles I tried to start up the pod with the containers having the issues above, and it just... worked. No more errors. Am I nuts? Or was "something" stale somewhere or whatever? How can I be sure this doesn't happen again? Is my method of backups sound? I am also backing up the volumes. mind is boggling |
Beta Was this translation helpful? Give feedback.
-
Evidence points to this not being a refresh issue, as I initially suspected. I'm now pivoting to the theory this is an EPERM joining the rootless CNI network namespace. It looks like this is an upgrade from an earlier Podman, so we have the new rootless CNI code interacting with the old CNI infra container, which I suspect is the cause. |
Beta Was this translation helpful? Give feedback.
-
FYI, I am available on Freenode as the nick Fieldy if there's anything I can do to assist. Thanks for all your work! |
Beta Was this translation helpful? Give feedback.
-
Well, the issue has returned, and like the other time, after a reboot. I have done other reboots between then and now and have not had issues until then. I have made attempts to perform backups and develop a restoration workflow in case this happens again. Can someone please review the above question about that workflow? #10036 (reply in thread)
|
Beta Was this translation helpful? Give feedback.
-
... Further, I tried to restore from backups into a new pod with a new network etc... And it's happened again. Is this a confirmed bug or something I'm doing wrong? This is keeping me from running a site and if I can't even get restorations to work, it's a roadblock. I'm on podman 3.1.0. I see that 3.1.1 is now available on alpine. Should I give that a try?
|
Beta Was this translation helpful? Give feedback.
-
I have time on my hands so tl;dr I replicated this in a virtual machine with 3.1.1. TL;DR: The issue still eventually happens.
|
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm getting the following issue starting a previously working pod with two containers in it. This only started after a kernel upgrade and reboot, in fact, the first kernel upgrade after installing podman.
I have looked around in all of the usual places, dmesg, system logs and so on and just have not found anything else interesting. The only for-sure thing is that this started immediately after the kernel upgrade and reboot.
I'm at a loss here :)
Searching around the internet hasn't revealed much, so I'll just get to the juicy stuff and give you:
Beta Was this translation helpful? Give feedback.
All reactions