-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
False address already in use #47944
Labels
area/networking/portmapping
area/networking
kind/bug
Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.
status/0-triage
version/26.1
Comments
Hi @Tohjuler, could you please enable debug mode (see here: https://docs.docker.com/config/daemon/logs/#enable-debugging) and post all revelant logs you find? |
This is the debug info from one of the containers that can't start
Can it be because |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/networking/portmapping
area/networking
kind/bug
Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.
status/0-triage
version/26.1
Description
After a restart of my server, some containers can't start because of Address already in use, but they ran fine before the restart.
And sudo lsof -i -P -n | grep LISTEN says that the port is not in use.
The bug has been there since 26.0.0, but sometime it will be fixed by restarting the server.
I haven't seen this bug on any other server.
I am considering reinstalling the server, but wanted to share the bug first.
Reproduce
docker start
Expected behavior
No response
docker version
Client: Docker Engine - Community Version: 26.1.4 API version: 1.45 Go version: go1.21.11 Git commit: 5650f9b Built: Wed Jun 5 11:29:35 2024 OS/Arch: linux/arm64 Context: default Server: Docker Engine - Community Engine: Version: 26.1.4 API version: 1.45 (minimum version 1.24) Go version: go1.21.11 Git commit: de5c9cf Built: Wed Jun 5 11:29:35 2024 OS/Arch: linux/arm64 Experimental: true containerd: Version: 1.6.33 GitCommit: d2d58213f83a351ca8f528a95fbd145f5654e957 runc: Version: 1.1.12 GitCommit: v1.1.12-0-g51d5e94 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Additional Info
Here is the output from
docker inspect
on one of the effected containers:I was told to run
sudo ss -tlpn 'sport = :5432'
with one of the affected ports, but it did not list anything.The text was updated successfully, but these errors were encountered: