Open derNiklaas opened 10 months ago
AFAICT this doesn't seem to be a compose issue, but a docker engine one. If you have a chance to reproduce, please try running docker run -p <SUPPOSED_TO_BE_CONFLICTING_PORT>:80 nginx
and confirm there's no issue doing so
A colleague is having the same issue and got the following output after running the docker compose command and then running your command:
docker: Error response from daemon: driver failed programming external connectivity on endpoint hardcore_diffie (98585ecb1e742b304c5453d48e48c679babad9ac9a55ae3081bb08cd5a989691): Error starting userland proxy: listen tcp4 0.0.0.0:8080: bind: address already in use
They also tried running it without the compose and it worked correctly for them
same!centos7
Client: Docker Engine - Community
Version: 26.0.1
API version: 1.45
Go version: go1.21.9
Git commit: d260a54
Built: Thu Apr 11 10:56:30 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 26.0.1
API version: 1.45 (minimum version 1.24)
Go version: go1.21.9
Git commit: 60b9add
Built: Thu Apr 11 10:55:26 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.31
GitCommit: e377cd56a71523140ca6ae87e30244719194a521
nvidia:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.19.0
GitCommit: de40ad0
@derNiklaas: I have stumbled upon a similar issue, but what I discovered was that I had two services setup towards a docker network, with one of the services configured with a static ipv4 assignment, while the other did not have a static IP assigned.
The result of this configuration was that sometimes (particularly after hard-resets of the host system, like power outages), the second service dynamically got assigned the IP that the first service was supposed to be assigned statically, causing the first service to fail to start with an error "Error response from daemon: Address already in use", which sounds eerily familiar.
Description
A few days ago, I tried to start my companies docker compose system and noticed that one service wasn't starting because Docker thinks the port was already in use. (
bind: address already in use
)After days of restarting and reinstalling Docker (+ compose), it started working again after deleting the cache files from Docker.
Steps To Reproduce
Unfortunately, this bug occured randomly and I don't know how to reproduce it
Compose Version
Docker Environment
Anything else?
No response