Docker compose refuses to attach multiple networks

bluepuma77 · February 24, 2024, 8:05am

There is already an issue on GitHub:

[BUG] Compose up often fails to join one random network on v2.24.6

opened 10:07AM - 21 Feb 24 UTC

kind/bug

### Description This may be closely related to #11510 but it seemed different… enough to open another issue. Whenever I run docker-compose up -d and one or multiple containers in the compose has multiple networks, it often randomly fails to join exactly one network. I have tried with internal, external and a mix of internal and external networks with anything between 3 and 10 networks and the result is always the same: About 60% of the time it fails to join exactly one network, the exact network is different. Tried on 2 different installations and both has the same result. I see nothing relevant in the container logs, journalctl or docker event. Reverting to 2.24.5 fixes this problem. ### Steps To Reproduce 1. Create docker-compose file with at least one container with multiple networks, for example: ``` version: "3.8" networks: test1: test2: test3: services: whoami: image: traefik/whoami container_name: whoami networks: - test1 - test2 - test3 ``` 2. run docker-compose up 3. run docker container inspect and count the networks Doing the above 10 times, the container joined all 3 networks 4 times and then only 2 networks 6 times (the missing network seemed random, either test1, test2 or test3) A quick way to test step 2 and 3: `docker stop whoami && docker rm whoami && docker compose up -d && docker container inspect -f '{{ len .NetworkSettings.Networks }}' whoami && docker container inspect -f '{{ range $key, $value := .NetworkSettings.Networks }}{{$key}} {{end}}' whoami` ### Compose Version ```Text Docker Compose version 2.24.6 ``` ### Docker Environment ```Text Client: Version: 25.0.2 Context: default Debug Mode: false Plugins: compose: Docker Compose (Docker Inc.) Version: 2.24.6 Path: /usr/lib/docker/cli-plugins/docker-compose Server: Containers: 54 Running: 4 Paused: 0 Stopped: 50 Images: 83 Server Version: 25.0.2 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: true Native Overlay Diff: false 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: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 7c3aca7a610df76212171d200ca3811ff6096eb8.m runc version: init version: de40ad0 Security Options: seccomp Profile: builtin cgroupns Kernel Version: 6.7.5-arch1-1 Operating System: Arch Linux OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 31.31GiB Name: PC ID: ZVFP:QROB:AMZD:7QXN:EBLS:QEAF:NVK2:NCJL:MJF5:GIXF:NQ4I:S5EH 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_

I really wonder how something like this can be missed in their quality control.

Topic		Replies	Views
NAT issues when defining multiple networks in docker-compose.yml Docker Desktop	3	1758	April 6, 2016
Intermittent silent fail at attaching a network Compose	2	289	August 16, 2023
Cannot create network (br-....) conflicts with (br-...): networks have overlapping IPv4 Compose	1	2553	March 11, 2021
Docker-compose : can't connect to existing network Compose	13	40453	April 1, 2021
Bind ports to networks individually Compose	0	1204	April 24, 2017

Docker compose refuses to attach multiple networks

Related topics