Windows: missing secrets file creates file-named directory [again]

[filimonic]

docker compose up creates folder named as secret file when file does not exist

> docker compose version
Docker Compose version v2.40.0-desktop.1
> docker compose up

name: test
secrets:
  sample_secret:
    file: ./sample.secret
services:
  sample:
    image: "alpine:latest"
    secrets:
      - sample_secret

I'm still seeing this problem with Docker Compose version v2.32.4-desktop.1 on Windows.

Originally posted by @Kylotan in #8305

[ndeloof]

Don't you get a warning ?

$ docker compose up
WARN[0000] secret file xx_sample_secret does not exist 

[Grimeh]

Also seeing this on Windows.

For me the issue isn't whether there's a warning or not but the fact that it creates an unwanted folder which must be manually deleted. This doesn't happen on other platforms afaik.
Ideally it would error out immediately if a secret source file doesn't exist, rather than just logging a warning and creating a folder for the bind mount.

[ndeloof]

indeed, on OSX I get

 ✘ Container truc-sample-1  Error response from daemon: invalid mount config for type "bind": bind source path does not exist...                           0.0s 
Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /host_mnt/Users/nicolas/xx/sample.secret

it seems engine doesn't respect the CreateMountpoint API parameter if you don't get such an error reported.
Let me try to reproduce on my Windows machine