Starting fresh demo fails for modern docker compose
The issue was found during 1.13 sanity checks by @slawek.
rake demo:up
fails:
deep@deep:~/Downloads/artifacts (62)/stork-1.13.0$ rake demo:up CS_REPO_ACCESS_TOKEN=...
docker compose --project-directory . -f docker/docker-compose.yaml -f docker/docker-compose-premium.yaml build
[+] Building 1.9s (8/8) FINISHED docker-container:stork
=> CANCELED [server internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
=> CANCELED [agent-kea internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
=> CANCELED [agent-kea6 internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
=> CANCELED [agent-kea-ha2 internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
=> CANCELED [agent-bind9-2 internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
=> CANCELED [kea-config-generator internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.7s
=> => creating container buildx_buildkit_stork0 0.2s
=> ERROR [agent-bind9 internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.8s
=> => creating container buildx_buildkit_stork0 0.1s
=> CANCELED [agent-kea-ha1 internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
------
> [agent-bind9 internal] booting buildkit:
------
Error response from daemon: Conflict. The container name "/buildx_buildkit_stork0" is already in use by container "aad862ed4f9cc3c211de2308c3475379f7f5e2835d646f4a7e5f78186e717d0a". You have to remove (or rename) that container to be able to reuse that name.
rake aborted!
Command failed with status (17): [docker compose --project-directory . -f do...]
/home/deep/Downloads/artifacts (62)/stork-1.13.0/rakelib/60_docker_demo.rake:98:in `docker_up_services'
/home/deep/Downloads/artifacts (62)/stork-1.13.0/rakelib/60_docker_demo.rake:116:in `block (2 levels) in <top (required)>'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
Tasks: TOP => demo:up
(See full trace by running task with --trace)
My setup:
$ docker version
Client:
Version: 24.0.5
API version: 1.41 (downgraded from 1.43)
Go version: go1.20.3
Git commit: 24.0.5-0ubuntu1~22.04.1
Built: Mon Aug 21 19:50:14 2023
OS/Arch: linux/amd64
Context: default
Server:
Engine:
Version: 20.10.24
API version: 1.41 (minimum version 1.12)
Go version: go1.20.7
Git commit: 5d6db84
Built: Wed Aug 23 20:55:00 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.6.20
GitCommit: 2806fc1057397dbaeefbea0e4e17bddfbd388f38
runc:
Version: 1.1.5
GitCommit:
docker-init:
Version: 0.19.0
GitCommit: de40ad0
$ docker compose version
Docker Compose version v2.21.0
$ docker buildx version
github.com/docker/buildx v0.11.2 9872040
Workaround: Call rake demo:build
and next rake demo:up
The same problem is described on StackOverflow.