Description
openedon Jun 7, 2024
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.
$> docker network ls
8e3c351af333 bridge bridge local
0cbc0420c111 docker_gwbridge bridge local
x8gb7mz6s222 swarm-overlay overlay swarm
c09ad17a7321 host host local
keth4xuub123 ingress overlay swarm
d8baa27f3654 none null local
Workaround:
The only solution I have found is to downgrade to an earlier version (2.21.0-1) of docker-compose-plugin
sudo apt list -a docker-compose-plugin
sudo apt install docker-compose-plugin=2.21.0-1~debian.11~bullseye
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.
...
service:
image: service-image
container_name: service
networks:
- swarm-overlay
restart: unless-stopped
...
networks:
swarm-overlay:
attachable: true
driver: overlay
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.
...
worker-service:
image: worker-image
container_name: worker-service
networks:
swarm-overlay:
aliases:
- host1-worker-service
restart: unless-stopped
...
networks:
swarm-overlay:
external: true
driver: overlay
docker compose up -d worker-service
This errors with:
Error response from daemon: network swarm-overlay not found
Compose Version
docker-compose-plugin/bullseye 2.27.1-1~debian.11~bullseye
Docker Compose version v2.27.1
Docker Environment
Client: Docker Engine - Community
Version: 26.1.4
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.14.1
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.27.1
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 12
Running: 5
Paused: 0
Stopped: 7
Images: 31
Server Version: 26.1.4
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: active
NodeID: 2brhg9vzj8m47oyo40ie5yj0u
Is Manager: false
Node Address: 1.2.3.4
Manager Addresses:
4.3.2.1:2377
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: d2d58213f83a351ca8f528a95fbd145f5654e957
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 5.10.0-28-cloud-amd64
Operating System: Debian GNU/Linux 11 (bullseye)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 13.42GiB
Name: cloud-machine
ID: 6c0ae974-1ba3-450a-ab03-d31b31c6097f
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Anything else?
No response
