-
Notifications
You must be signed in to change notification settings - Fork 246
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
counter: check for external umounts #698
Conversation
if a previously mounted container was unmounted externally (e.g. through conmon cleanup for Podman containers), the ref counter will lose track of it and report it as still mounted. Closes: containers#697 Signed-off-by: Giuseppe Scrivano <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recall doing something like this a while ago. But @nalind I believe did not like it. I will see if I can find the PR.
I don't like it too :-) but cannot think of a better way beside changing how podman/conmon cleanup work |
LGTM |
This fixes a critical bug we found in the Podman REST API tests. Can we prioritize getting this in? |
This isn't going to fix everything, but it's a step in the right direction. LGTM. |
Cherry-pick #698 into v1.20-stable
if a previously mounted container was unmounted
externally (e.g. through conmon cleanup for Podman containers), the
ref counter will lose track of it and report it as still mounted.
Closes: #697
Signed-off-by: Giuseppe Scrivano [email protected]