-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[BUG] Overlay network not found on worker node #11894
Comments
This isn't the same issue as #11387 as here this is the docker engine reporting error: Can you please confirm you can use |
I'm running into this exact same issue using Docker Compose 2.27.0. I can confirm that I can use However, using docker compose files, I also get the error |
I am having the exact same issue. |
btw is the downgrade workaround needed for both leader and worker node? |
@inql I have not tested this as our scripts set versions for all nodes. |
Hey there, also affected by this bug. If you don't want to downgrade another workaround is to create a container and attach it to the network. It then appears in the list and docker compose no longer complains
Adding My versions in case it is useful:
|
As in above, sorry did not realise that @michaelmcandrew also mentioned this but at least this comment confirms his findings: #11894 (comment) I tested this issue and noticed that if there exists running container which has connection to the external overlay network (started with So, without knowing anything about internals, the problem might have something to do with not checking for available external overlay networks but instead checking just internal networks (visible with docker network ls). So as an additinal workaround it is possible to first start "dummy" container on workers via for example:
I also checked downgrading and for Ubuntu 22.04 it worked, so I think I will be using downgraded version for now myself.
|
@kulpsin Lines 1334 to 1340 in 11d5ecd
Not sure why this doesn't work as expected, need to setup a test environment and try to reproduce this bug |
To flesh out my steps to reproduce a bit more, since they are slightly different from the ones mentioned above, I created a swarm network on the lead node with This network was not visible on the worker node (expected I think because nothing was connected). However, I was not able to connect to it with the below networks section in a
I created the following container on the worker node I was then able to connect using the above networks section in a Hope that help with the reproduction! |
Description
Issue:
Swarm worker hosts fail to attach to manager node overlay networks unless a container has been manually started and attached to the network using
docker run --network swarm-overlay
Expected Behavior:
This should automatically attach to the overlay network and it should be visible in the docker network info.
Workaround:
The only solution I have found is to downgrade to an earlier version (
2.21.0-1
) ofdocker-compose-plugin
I believe this is the same issue as #11387 but i couldn't find any open bugs with the same issue.
Thanks for any help with this!
Steps To Reproduce
I created a custom overlay network on the swarm manager node.
This correctly created the network and attached the relevant container to it.
I then joined a worker host to the swarm and attempted to connect a container to the overlay network.
docker compose up -d worker-service
This errors with:
Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: