Repository navigation
[BUG] The new service: directive does not work with docker compose up --build #12822
Description
Activity
The fix sufficed for run, but up is still broken.
pkgx [email protected] docker-compose up --build b Compose can now delegate builds to bake for better performance. To do so, set COMPOSE_BAKE=true. [+] Building 0.0s (1/1) FINISHED docker:desktop-linux => [b internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 88B 0.0s failed to solve: invalid reference formatCOMPOSE_BAKE=true pkgx [email protected] docker-compose up --build b [+] Building 0.0s (1/1) FINISHED => [internal] load local bake definitions 0.0s => => reading from stdin 442B 0.0s failed to find target aAnd here is the run case which is now fixed:
pkgx [email protected] docker-compose run --build b [+] Creating 1/1 ✔ Network delme3_default Created 0.0s Compose can now delegate builds to bake for better performance. To do so, set COMPOSE_BAKE=true. [+] Building 1.9s (12/12) FINISHED docker:desktop-linux => [a internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 85B 0.0s => [a internal] load metadata for docker.io/library/alpine:latest 1.4s => [a internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [a 1/1] FROM docker.io/library/alpine:latest@sha256:a8560b36e8b8210634f77d9f7f9efd7ffa46 0.4s => => resolve docker.io/library/alpine:latest@sha256:a8560b36e8b8210634f77d9f7f9efd7ffa463e 0.0s => => sha256:8d591b0b7dea080ea3be9e12ae563eebf9869168ffced1cb25b2470a3d9fe15e 597B / 597B 0.0s => => sha256:6e771e15690e2fabf2332d3a3b744495411d6e0b00b2aea64419b58b0066cf 3.99MB / 3.99MB 0.3s => => sha256:a8560b36e8b8210634f77d9f7f9efd7ffa463e380b75e2e74aff4511df3ef8 9.22kB / 9.22kB 0.0s => => sha256:757d680068d77be46fd1ea20fb21db16f150468c5e7079a08a2e4705aec096 1.02kB / 1.02kB 0.0s => => extracting sha256:6e771e15690e2fabf2332d3a3b744495411d6e0b00b2aea64419b58b0066cf81 0.1s => [a] exporting to image 0.0s => => exporting layers 0.0s => => writing image sha256:c8fcc9024fc26421206f8759e1f46caf8816bee3f19a2050abb4b8a2edf95d62 0.0s => => naming to docker.io/library/service_a 0.0s => [a] resolving provenance for metadata file 0.0s => [b internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 88B 0.0s => [b context service_a] load metadata for service_a 0.0s => [b internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => CACHED [b context service_a] service_a 0.0s => [b] exporting to image 0.0s => => exporting layers 0.0s => => writing image sha256:31e5d591c3bf5787ce7319e062bcd66833f378db9b885c13b4d04eaaaf956536 0.0s => => naming to docker.io/library/service_b 0.0s => [b] resolving provenance for metadata file 0.0s / #
Description
The new service directive is almost functional after the fix of #12783. Now I can run
docker compose build bwhere b has an additional context in the form of "service:a". However, runningdocker compose run --buildor other variants still fail.Steps To Reproduce
Here is a repro adapted from https://stackoverflow.com/questions/37933204/building-common-dependencies-with-docker-compose/79487072#79487072 and already used in #12783.
And here are the failures. I am using
pkgxto explicitly select doker compose v2.36.0, which already contains the fix for #12783.It would be super cool if eventually even
docker compose up --watch --build bworked.Compose Version
Docker Environment
Anything else?
I would have reopened #12783 if I had the powers since the bugs are closely related. But since I don't, I brought it here.