-
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 containers running in "Created" status #11539
Comments
Since I'm running rootless podman, here's the output of
|
Likely cause: It looks like you're on a RHEL/Cent 8.4 system, which means systemd as PID 1. Systemd periodically clears out directories in Can you verify whether |
Hi and thank you for your reply. It is indeed a RHEL 8.4 system. The file you mention does exist and below are its contents:
|
I've been checking the
It shouldn't be the problem, but the ten days age fits with the fact that the 7-days old containers are still in a consistent state and the 13 days old containers are in an inconsistent state. According to the This is the only path pattern that would match I'll be checking the containers again in about three days. At this point honestly I think that it would probably be better to have that run root residing somewhere else. @mheon can I change that to be somewhere like |
@mheon I tried setting age to I'm now 99% sure that's the problem. Running
Needless to say, the first I'd say this is a smoking gun. |
This is the same issue as #11478. What you really need to do is run |
I did perform |
/kind bug
Description
As a non-root user, having started some containers, after a few days they will appear in "created" state but are actually running.
This is somewhat a duplicate of issue #11478 except i'm using neither systemd nor
podman play kubernetes
to start pods.Steps to reproduce the issue:
Use any docker-compose.yml file, launch some containers
wait some days
run
podman ps -a
Describe the results you received:
Also by inspecting a sample container:
It's not Running, it's not Paused, it's not Restarting, its not OOMKilled, it's not dead. There's no pid.
This does not look like a consistent behavior yet podman doesn't even emit a warning or anything.
Describe the results you expected:
I expect to see the containers still up:
Additional information you deem important (e.g. issue happens only occasionally):
It's been a while, happens almost regularly.
The problem is that I cannot exec into containers or follow the logs from the command line.
Output of
podman version
: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? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes.
At the time of writing there's no update candidate for podman in RHEL. I just tried running
yum update podman
just to be sure.I have checked the troubleshooting guide, I didn't find anything matching the description of my problem.
Additional environment details (AWS, VirtualBox, physical, etc.):
In my system (RHEL 8.4 installed on a physical computer) the only peculiarities are:
The text was updated successfully, but these errors were encountered: