Nicolas De loof
Nicolas De loof
@crazy-max looking at failing test I guess this is an issue we need to fix on Compose as well
I'm not sure I understand the fix covered by TestReadTargetsWithDotCompose. `sanitizeTargetName` to convert `web.app` with `web_app` then merge targets with same resulting name, while those were distinct in compose
Can't reproduce ``` $ ls -l test total 32 -rw-r--r-- 1 nicolas staff 30 5 mai 08:34 compose.yaml -rw-r--r-- 1 nicolas staff 12 29 avr 09:20 Dockerfile $ ls -l...
maybe specific to WSL when symlink points to a distinct windows drive ?
Can you please try running with `COMPOSE_BAKE=true` variable set ?
> However this issue happens also when in the real folder Ouch. Unrelated to this issue then, but could you please run `COMPOSE_BAKE=true docker compose --verbose build` to capture the...
> failed to evaluate path "D:\\dev\\test-docker/D:\\dev\\test-docker\\Dockerfile this is actually https://github.com/docker/compose/issues/12669, fixed by https://github.com/docker/buildx/pull/3141
is `C:\Users\Admin\dev\test-docker` the actual path to your build context or the symlink location ? Can you confirm `docker build .` is successful when ran from this folder ?
probably same cause as https://github.com/docker/compose/issues/12891 `docker build .` has [some dedicated code](https://github.com/docker/cli/blob/9e506545fdead79c574345a0414c71a0bd6857d6/cli/command/image/build/context.go#L256) to manage various corner cases that needs to be replicated
Thanks for reporting this, I'll look into this ASAP