Nicolas De loof
Nicolas De loof
we could copy secret again at any time, or have a dedicated command for this purpose, but the more obvious one would be to trigger a container `restart`
Marking this issue as "kind/enhancement" as secrets never have supported having uid/gid set by compose (v1 or v2), this feature was introduced and only supported by docker swarm
@con-f-use I'm not talking about a Dockerfile `COPY` but about using `docker cp` after the container has been created. It won't be stored inside an image
@ianhinder yes indeed
using bind mount for local files indeed doesn't work with a remote docker host, and is a significant limitation for this use-case
actually you _can_ `docker cp` into a container before after it has been created and before it get started
indeed, this has been inherited from the legacy docker compose v1 documentation, by the time it was converted into "compose specification". Better fix the docs then
Closed as obsolete
Do you have the same issue running `DOCKER_BUILDKIT=1 docker build -f A.Dockerfile . && docker build -f B.Dockerfile .` ? (in such case, this is a buildkit issue) Compose v2.1.x...
@nickcoad Do you have the same issue running DOCKER_BUILDKIT=1 docker build -f A.Dockerfile . && docker build -f B.Dockerfile . ? I understand the frustration with this issue, but without...