Open elipp opened 6 days ago
This is indeed related to buildkit being used to run the build. Buildkit is not aware of dependencies between those two service image and want to build those in parallel, which causes this failure.
As a workaround, you can declare a dependency between services using depends_on
. While this might not be relevant at runtime, Docker Compose will then build images in sequence
Description
Using a present, locally
docker run
:able image as the FROM stage in a Dockerfile results in docker compose trying to pull the image and failing. See Steps to Reproduce.Steps To Reproduce
docker.compose.yml:
Dockerfile.someimage:
Dockerfile.service1:
Running
docker compose build someimage && docker compose build service1
results in:docker buildx container logs:
Using
DOCKER_BUILDKIT=0 docker compose build
builds the image just fine, same goes for:This also happens if the image name is hard-coded (not passed as an ARG).
Compose Version
Docker Environment
Anything else?
Could be a BuildKit issue since DOCKER_BUILDKIT=0 works...?
UPDATE: this actually works if I use the "default" docker buildx driver/endpoint (and fails with the
docker-container
) one.