Skip to content

podman restart with port bindings results in 'port in use' errors #240

@baude

Description

@baude

Sometimes when restarting a container with podman restart, it results in a port already in use error. It seems like you need to have an application in the container that takes a little longer to execute to trip it more reliably.

Reproducer

$ sudo podman run -dt --name foo -p 80:80 alpine_nginx
b7fc4ef1bc8a130ec0dec234c59bc11a7d6e88b24e48d04e8afede3b832db3db
$ sudo podman restart foo
Error: cannot listen on the TCP port: listen tcp4 :80: bind: address already in use

split from containers/podman#9465

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions