-
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
The podman start --attach
command should not print ID
#7068
The podman start --attach
command should not print ID
#7068
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mheon 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 |
Somewhere in the Podman v2 rewrite, we allowed `podman start --attach` to print the container ID of the started container after exiting from the attach session (via detach key or the container exiting naturally). We should never print the ID when `--attach` is given, which makes the fix simple - make the print statement conditional on `--attach` not being present. Wierdly, this only happened with `--interactive` was given to `podman start`. I don't know why that is, but this resolves the issue without having to dig any deeper, so I'm content. Fixes containers#7055 Signed-off-by: Matthew Heon <[email protected]>
14e1983
to
099649a
Compare
LGTM |
1 similar comment
LGTM |
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.
/lgtm
Screams for a test though.
Somewhere in the Podman v2 rewrite, we allowed
podman start --attach
to print the container ID of the started container after exiting from the attach session (via detach key or the container exiting naturally). We should never print the ID when--attach
is given, which makes the fix simple - make the print statement conditional on--attach
not being present.Wierdly, this only happened with
--interactive
was given topodman start
. I don't know why that is, but this resolves the issue without having to dig any deeper, so I'm content.Fixes #7055