docker run -v on Windows for volume mount works via cli but not via script calling same command

Description

The following 'docker run' command works fine from Windows CLI:

docker run -d --name <name> -p <port>:5432 -v <abspath>:/<container_path> postgres:latest

For the -v I have "/c/Users/user/directory with spaces/dir/dir/dir:/remote-path".

Using a python script, calling with subprocess.run() with the exact same arguments, it gets various docker errors.

I was able to get it to work in another directory with no quotes where there were no spaces in the directory names. Using it with quotes confused it again. But can't use that directory permanently either way.

I've tried using C:\Users\ etc, etc instead, I've tried with and without quotes in the whole thing or just the local path, and nothing works. I get various error messages between it trying to tell me my absolute path is not an absolute path, invalid format, and invalid mode.

Perhaps user error here but no matter what I do I get some sort of docker run error using -v from script, whereas from CLI directly it runs fine with the exact same command.

One example error:

docker: Error response from daemon: create "/c/Users/<user>/dir with spaces/dir/dir/dir: "\"/c/Users/<user>/dir with spaces/dir/dir/dir" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path.

But again with the same path, don't get this from CLI directly.

Reproduce

1. Run from CLI, see that it works.

    docker run -d --name postgres-test -p 15432:5432 -v "/c/Users/<user>/dir with spaces/dir/dir/dir:/docker-entrypoint-initdb.d postgres:latest
   

2. Run via code, see that it fails.

Something like:

command = ['docker', 'run', '-d', '--name', 'postgres-test' '-p', '15432:5432', '-v',
                      '"/c/Users/<user>/dir with spaces/dir/dir/dir:/docker-entrypoint-initdb.d" ',
                      'postgres:latest']
subprocess.run(command, text=True, timeout=10.0, capture_output=True)

This fails whether I use quotes or not, where I put the quotes, if I switch the local path to C:\Users\<user>\dir with spaces\dir\dir\dir.

Expected behavior

Running via script calling the same command should have the same result? Unless I am being dumb and doing something very wrong / noobish, which is always possible.

docker version

Client:
 Cloud integration: v1.0.35+desktop.13
 Version:           26.1.1
 API version:       1.45
 Go version:        go1.21.9
 Git commit:        4cf5afa
 Built:             Tue Apr 30 11:48:43 2024
 OS/Arch:           windows/amd64
 Context:           default

Server: Docker Desktop 4.30.0 (149282)
 Engine:
  Version:          26.1.1
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.9
  Git commit:       ac2de55
  Built:            Tue Apr 30 11:48:28 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.31
  GitCommit:        e377cd56a71523140ca6ae87e30244719194a521
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    26.1.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.0-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.27.0-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.29
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.23
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.1.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.8.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 3
 Server Version: 26.1.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e377cd56a71523140ca6ae87e30244719194a521
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.15.146.1-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.6GiB
 Name: docker-desktop
 ID: da376867-cd51-4c0d-acd6-0deb74ea2540
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=npipe://\\.\pipe\docker_cli
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile

Additional Info

No response

Start by comparing the working CLI command with the shown Python subprocess.run argument list, including its quoting and separators. Reproduce the failure with the listed Docker Desktop versions and confirm whether the same arguments reach Docker; done means a minimal confirmed Docker CLI defect, rather than an invocation-specific issue.