-
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
Filling up /run/libpod/socket #3962
Comments
This sounds like Conmon control FIFOs and attach sockets - but those should be deleted once the container exits. Are you running Podman as root, or without? Can you do an |
All containers were up, none of them exited during the period files were piling up. This is a new install, never done any upgrade or anything, but stopping all containers and running
I'm running as root. I did a |
It is doing that again. So far I remember doing some
|
I think I've been able to isolate it a little further. there's one container on my stack which has a healthcheck instruction, these socket files start piling up exactly after it has started. |
Probably artifacts from |
The healthcheck instruction looks like this:
It's currently |
It makes sense how easily it's filling the tmpfs - we're getting... I think 3? separate files per exec session, and for some reason they are not being cleaned up. Add to that an exec every 3 seconds and we rapidly begin to accumulate files. |
yeah the exec artifacts should removed after an exec session. can you exec that command in the container and let me know if an error along the lines of |
There should also be logs available in |
|
Interesting. My assumption here would be that |
Looks like fixing my broken healthchecker did not have an effect on this issue. |
Investigating further - going to try to get a fix into 1.6.0 |
when executing a healthcheck, we were not cleaning up after exec's use of a socket. we now remove the socket file and ignore if for reason it does not exist. Fixes: containers#3962 Signed-off-by: baude <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
Describe the results you received:
It appears that socket files from health checks aren't being cleaned up.
Describe the results you expected:
Not fill up
/run
.Additional information you deem important (e.g. issue happens only occasionally):
Still reproducible across reboots,
podman system prune
s, etc.Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
Orange Pi Zero running armbian stretch (I know)
The text was updated successfully, but these errors were encountered: