Nicolas De loof
Nicolas De loof
@cideM see https://github.com/compose-spec/compose-spec/blob/main/build.md#ssh
Let's keep this one opened to collect feedback and integration proposals
I wonder this could be addressed using a top-level `images` attribute as suggested by https://github.com/compose-spec/compose-spec/issues/188
sorry for the terrible delay without answer on this issue. Most of the examples shared in comments use Compose v1, with or without buildkit enabled. Compose v1 will be End...
closing as unclear and obsolete. If you encounter a comparable issue, please create a fresh new one with details on your environment
Your `docker run` command isn't equivalent to `docker compose up` as it uses the `--mount` flag. Can you please try to use `docker volume create ...` to create the NFS...
compose equivalent would be: ```yaml (...) volumes: - source: ./web/dist target: /usr/share/nginx/html volume: # this is not supported by the spec, seems nobody asked for it 😅 ```
Thanks for this detailed description, I'll try to reproduce and investigate
I checked `docker compose up` sends the exact same API payload to `VolumeCreate` engine API vs `docker volume create...`. I can't find any way to explain this weird behavior 😢
maybe a race condition ? could you try running `docker volume create (...) && docker run -v ...` so there's no delay between those two commands