Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#69367 - [docker] Keeps bound port after container exited
Attached to Project:
Community Packages
Opened by Iván Perdomo (katratxo) - Tuesday, 19 January 2021, 13:08 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 20 January 2021, 12:14 GMT
Opened by Iván Perdomo (katratxo) - Tuesday, 19 January 2021, 13:08 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 20 January 2021, 12:14 GMT
|
DetailsDescription:
The published ports to the host machine keep bounded (in-use) after the container has exited. Restarting the service makes the problem go away. Additional info: * Package version: docker-1:20.10.2-3 * docker --version Docker version 20.10.2, build 2291f610ae Steps to reproduce: Start a container publishing some port and then exit it $ docker run --tty --interactive --rm --publish 3000:3000 alpine:3.12 / # ^D (or exit) Try to do the same operation, another container publishing the same port: $ docker run --tty --interactive --rm --publish 3000:3000 alpine:3.12 docker: Error response from daemon: driver failed programming external connectivity on endpoint exciting_cray (f133e4a4f593120300b70fac45ab1bd31cef071232546a6f8091f8998c012e39): Bind for :::3000 failed: port is already allocated. Restart the docker service # systemcl restart docker Now you can start again the container $ docker run --tty --interactive --rm --publish 3000:3000 alpine:3.12 |
This task depends upon
Closed by Doug Newgard (Scimmia)
Wednesday, 20 January 2021, 12:14 GMT
Reason for closing: Fixed
Additional comments about closing: docker 1:20.10.2-4
Wednesday, 20 January 2021, 12:14 GMT
Reason for closing: Fixed
Additional comments about closing: docker 1:20.10.2-4
Downgrading `docker` from `1:20.10.2-3` to `1:20.10.2-2` is working for me.
[1]: https://github.com/archlinux/svntogit-community/commit/7ad6147e8cbbadac39011ca9efb713598c8f33a6#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a