Nicolas De loof
Nicolas De loof
docs has been updated with a better description for the (complex, sorry, legacy...) logic used to define project name https://docs.docker.com/compose/reference/#use--p-to-specify-a-project-name
I'm closing this issue as obsolete: Docker Compose V1 has reached end-of-life and we are not accepting any more changes. Please try and reproduce your issue with Compose V2 and...
please try reproducing this build failure using `docker buildx build ...` for your Dockerfile. If you get the same issue failing to pull base image, then this is a buildkit...
@yrsh can you please try building directly your Dockerfile with buildkit enabled ? (run `docker buildx build ... `)
AFAICT we need to make the `ContainerCreate` API calls sequential to enforce a distinct port is assigned
`docker-compose down` does not remove volumes, so if you use those, data won't get lost. Introducing a confirmation to `compose down` would be a significant compatibility break which will have...
don't you have the same error when image is built using recent docker CLI as `docker build ...` with engine 19.03? that's weird anyway, as those image attributes are all...
Closing as reporter didn't provided the requested informations
right, you just answered. Wasn't obvious you don't have the same issue with plain `docker build`. I can't reproduce this issue, so hard to diagnose: ``` $ docker run -d...
Have you tried using the classic builder by running `DOCKER_BUILDKIT=0 docker compose build` just in case this issue is related to buildkit being used by default with compose ?