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
Container does not get automatically removed as specified by the --rm flag after failing due to a --publish port already in use #15049
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jul 24, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jul 24, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Thanks for the report, @eriksjolund! It's definitely a bug. Since @rhatdan is already working on it, I am assigning the issue to him. |
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jul 25, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jul 25, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jul 25, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jul 25, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jul 25, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jul 26, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jul 26, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jul 28, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Aug 10, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com> <MH: Fixed cherry-pick conflicts> Signed-off-by: Matthew Heon <mheon@redhat.com>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Aug 10, 2022
Fixes containers#15049 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com> <MH: Fixed cherry-pick conflicts> Signed-off-by: Matthew Heon <mheon@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 20, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Container does not get automatically removed as specified by the --rm flag after failing due to a --publish port already in use. It works differently with Docker. After running the same command with Docker the container does not exist afterwards.
(I'm not quite sure, maybe this is less of a bug and more of a feature request?)
Steps to reproduce the issue:
Describe the results you received:
The container testing2 exists (as shown by the command
podman container list -a
)Describe the results you expected:
The container testing2 shouldn't exist.
Additional information you deem important (e.g. issue happens only occasionally):
I did a test with Docker on macOS Monterey 12.5:
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: