-
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
Handle --rm when starting a container #8688
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@edsantiago @mheon I am not sure this is the correct behaviour. IE Should failing to start, remove an autoremove container? podman run -rm fedora foopodman create --name test1 --rm alpine foo;podman start test1Both remove it, so for consistancy podman-run create --name test1 --rm alpine foo;podman-run start test1 Will also. |
@rhatdan I think we should probably preserve the behavior documented in
|
Ugh. Thinking it over some more, I'm uncertain what "started successfully" means. I could argue that getting to the point where the container says "dude, no such command" is a successful execution of the container. This is too tricky for me to think about at the end of a long week... |
From everything we've done so far, I think the expectation is that autoremove always removes, even containers that error. Recommendation: we should retain existing behavior and just remove that bit from the manpage. |
@containers/podman-maintainers PTAL |
SGTM but I agree with @mheon: those two sentences need to be removed from the manpage. |
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.
Code LGTM but I'd love a test or two.
podman start should follow the same behaviour as podman run when removing a container. Signed-off-by: Daniel J Walsh <[email protected]>
LGTM |
podman start should follow the same behaviour as podman run when removing a
container.
Fixes: #7746
Signed-off-by: Daniel J Walsh [email protected]