Nicolas De loof

I created https://github.com/docker/cli/pull/6573 to make it easier confirm such regression is a docker engine or compose issue in the future

I was able to reproduce this issue on Windows with Docker Desktop 4.49, checked that compose sets the expected `CreateHostPath` flag to false setting container mounts. Sounds like a Docker...

I can confirm a bug exists on Docker Desktop Windows (not compose fault 😇): ``` C:\Users\nicolas\test>dir 06/11/2025 10:48 . 06/11/2025 10:05 .. 04/11/2025 16:30 157 compose.yaml C:\Users\nicolas\test>docker run --mount type=bind,source=C:\Users\nicolas\test\sample.secret,target=/foo...

Agree this is a bug. The bug is not in compose, which use mount API for secrets, but in Docker Desktop as demonstrated by reproduction example https://github.com/docker/compose/issues/13310#issuecomment-3496207077 About https://github.com/compose-spec/compose-spec/pull/599, compose...

note: Internally tracked as https://docker.atlassian.net/browse/PRS-891

sounds like a (distinct) bug. default value bing true make the marshaller ignore `false` value - this was a design mistake of mine 😅

For legacy reasons 🥲 compose syntax didn't introduced an explicit `mount` attribute to match the docker/cli flags, so Compose has to select the engine API (`Bind` or `Mount`) to use...

> Is there an intentional seperation between docker's semantics and capabilities and docker compose's? nope, this is all legacy from Docker Swarm to adopt and tweak the compose file format...

We had this one in mind as we introduced service hooks, just delayed to check adoption and actual usages

Can you reproduce when docker swarm is disable ?