Description
Since I've run the E2E suite a bunch today, I've noticed the ddev test fails intermittently when bringing up the project:
Failed to start 004: ComposeCmd failed to run 'COMPOSE_PROJECT_NAME=ddev-004 docker-compose -f /tmp/TestComposeRunDdev2386477416/004/.ddev/.ddev-docker-compose-full.yaml up --build -d', action='[up --build -d]', err='exit status 1', stdout='#1 [web internal] load build definition from Dockerfile
Network ddev-004_default Creating
Network ddev-004_default Created
Container ddev-004-web Creating
Container ddev-004-dba Creating
Container ddev-004-db Creating
Error response from daemon: container 434c66ed5ce1c8b0a230b1ba25ac0b5cbedfc62710f3fbe01c0000d8fe2e2f80 is not connected to the network ddev_default'
That's coming from here:
|
err = s.apiClient().NetworkDisconnect(ctx, netwrk.Name, created.ID, false) |
When I modified the test locally to leave things running, I could see that the container was in fact connected to the network, so I think this is another Engine race condition with networks given that we create the container just before this
Steps To Reproduce
Run TestComposeRunDdev E2E test a bunch
Compose Version
Docker Environment
Occurs on both Engine v20.10.x in CI and v24.x locally on my macOS Docker Desktop install
Anything else?
No response
Description
Since I've run the E2E suite a bunch today, I've noticed the ddev test fails intermittently when bringing up the project:
That's coming from here:
compose/pkg/compose/convergence.go
Line 565 in 5155d22
When I modified the test locally to leave things running, I could see that the container was in fact connected to the network, so I think this is another Engine race condition with networks given that we create the container just before this
Steps To Reproduce
Run
TestComposeRunDdevE2E test a bunchCompose Version
Docker Environment
Anything else?
No response