Bug 1775647
| Summary: | Podman can't reuse a container name, even if the container that was using it is no longer around | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jian Zhang <jiazha> |
| Component: | Containers | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED ERRATA | QA Contact: | weiwei jiang <wjiang> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.z | CC: | amurdaca, aos-bugs, dwalsh, jnovy, jokerman, mheon, mpatel, nagrawal, smilner, tsweeney, walters |
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | podman-1.6.4-7.rhaos4.4.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-04 11:16:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1807437, 1807438, 1807439, 1807440, 1807441, 1807442 | ||
| Bug Blocks: | |||
|
Comment 4
Tom Sweeney
2019-12-02 19:47:31 UTC
It should be fixed in the next post Podman-1.6.3 release correct? I'll answer for Matt, yes this will be in in the first release after Podman 1.6.3, either 1.7.0 or 1.6.4. checked with reproducer https://github.com/containers/libpod/issues/3906, can not reproduce this issue. # rpm -qa|grep -i podman podman-1.6.4-8.rhaos4.4.el8.x86_64 # python3 poc.py Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^Ce0b198a25c9f3498d15d3491c93c37633be9912ada506210b590965e2686f7b2 Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^C4f5a50d6431d9f7bb305dbc427b2c630b9cf6eb11c86f862cc7d4687c26634df Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^Cf9b671614bb5afaeccf17bd2033ab04f454768f6cf49e3b69e479e0e5740990b Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^Cffbf681d023a2f5d3f71ab9f008f9a8228731f67e91dbe960e177e9af7d8ebfc Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^C44df58dd804f8ed20698339df8931c8ed5c1edbfa2a8436b345a31d497cccd91 Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^CError: can only kill running containers. d7e15c5d880c3f4b2806fafafc08e3266af6e106552aa31ac72ad48eda5a4325 is in state stopped: container state improper Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^Cb5f70df0936778b035eadbbee5781e7ecf70f54b136de105069e8d0524f25e89 Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^C42a91a1e42c33f91c071ff4b590bcff2dcc7c8b54c34eb918bf1968527c658d8 Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^Cab168e963237e25575b9f5103b180b611791b9e8a931b08123b03089c4d17db9 Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^C9d1928334708d2b3d2a4cba0971ca0348d63b8349b6f5f240514550c57ba816d Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^C9e5815f2e879f8d7ad31b8bb6cc6a658a6d1a1a3eaf0f3ffc77544392e5e2049 Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^Ce77029de2f875fd9c5489fee6a24764293cf987642d0a1369cbe5bdbb0bcc65a Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^Cf5776d2e656109aafc6a56e5f6989f0cf36883567135ace6d2f2bc9416e4375c Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^Ccbe028b305bea318b82985f2b23360b06c5ce24c6ae0b9f8bcd64123e9234d93 Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^Cccdc59b4abddf511a45f8cbb2d8efbf5d684bed671157d8d0832f403bf8a5b4b Press ctrl-C if http server start... Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ... ^C6f84bcdc10a4a3989a864c54c6434686a1d2d4c5753ed919977c795b66636313 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |