-
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 stop --ignore returns an error if --cidfile argument is used #19546
Comments
Thanks for reaching out, @rbagd. Since you reported using RHEL. If you desire a backport, please go through the Red Hat customer channels (e.g., Bugzilla). We can fix the issue upstream but backporting is up to the respective downstream distributions. |
Podman 4.6.0 fails as follows:
I think Podman should ignore the cidfile error with --ignore. @rbagd is this error message what you're seeing in 4.4.1 as well? |
@vrothberg, yes, that's the error. I think that's a regression from v4.3 as I didn't notice any issues with RHEL 8.7. |
Podman should ignore failures to find a cidfile when stoping the container if the user specified --ignore Fixes: containers#19546 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Looks like |
Podman should ignore failures to find a cidfile when stoping the container if the user specified --ignore Fixes: containers#19546 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Podman should ignore failures to find a cidfile when stoping the container if the user specified --ignore Fixes: containers#19546 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Issue Description
We noticed this issue after upgrade to RHEL 8.8 and podman v4.4.1, when timer-driven systemd services kept restarting. It turns out that this line in systemd service file kept failing with an error
I am not able to test with latest upstream at the moment.
Steps to reproduce the issue
Steps to reproduce the issue
podman stop --ignore --cidfile=whatever.cid
# should not return any errors but doesecho$?
# returns 125On the other hand,
podman stop --ignore nonexistent-container
exits with0
.Describe the results you received
Error was returned, even though it should be ignored. systemd services kept restarting because of it.
Describe the results you expected
Error should not be returned and
podman stop --ignore
should exit with0
.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: