Repository navigation
Network gateway: Address already in use #8742
Description
Activity
- added 2 commits that reference this issue
on Oct 4, 2021 We had to pin docker-compose to 1.29.2 in our CI due to this bug :(
Running into the same issue here.
Tried it on Ubuntu Linux and Docker Desktop for Mac (Version 4.1.1) - both compose files work like a charm if I use the python compose implementation. Also the version of the compose file does not seem to have an influence neither. Reproduced the "bug" on all of the available compose versions (from 3.8 down to 2.0).
Edit: Updated to Docker Desktop for Mac Version 4.2.0 today. Bug is still present in this version.
Same issue here. Docker Desktop for Mac (version 4.1.1). Docker Compose version v2.0.0.
I have
gateway: 172.30.0.254in the configuration file but it seems to ignore it and assigns IP172.30.0.1to the gateway which, by the way, was the static IP of one of the containers on the network and I getError response from daemon: Address already in use.It worked with previous versions of compose.
I think that the best approach ais that you simply find what is listening on that port. Depending on the system there are ways to check it (can be easily googled). Can you post here what is listening on the port ? Is it another breeze started (breeze stop should help with it) or another process ? Can you let us both know?
I'm running into this issue just by using
gateway: 10.8.1.1. No matter what we try it doesnt use the gateway we provide.We waited a few months before committing to migration to compose v2 and this bug essentially broke our whole infrastructure. Debating wether to just fork v1 and forget about v2 with the amount of bugs.
When using
10.8.1.1the container gets started with10.8.0.0as gateway. Our netmask is255.255.0.0.We still havent been able to upgrade to compose v2 becuase of this bug, still stuck with
1.29.2.Will this ever get fixed? We still stuck with
1.29.2...@gaby Hopefully yes ;-) @qnap-ericfan has opened a pull request with a fix : #9363
- added a commit that references this issue
on Oct 9, 2022 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as not stale anymore due to the recent activity.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Tested with latest release v2.18.1:
docker network inspect reports the expected gateway being set
"IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "10.10.1.0/24", "Gateway": "10.10.1.100" } ] },
issue indeed has been fixed by #9363, so closing
Reacted by Eirik Brandtzæg
Description
Trying to set a gateway to a specific address, but it won't be set.
If I try to set it to
10.10.1.100the bridge adapter will still be set to10.10.1.1.This worked fine in v1, so unless the configuration have changed it could be a bug in v2.
Example:
Steps to reproduce the issue:
docker-compose.ymlwith contents as described abovedocker-compose upDescribe the results you received:
Describe the results you expected:
No error
Output of
docker compose version:Additional environment details:
Tested on two different computers. Both running Arch Linux. Both Docker and Compose are from pacman.