Bind of volumen to project dir and relatives as volume does not work since 4.17.0

[leo-schick]

I upgraded to 4.17.0 (99724) and since then I cannot bind any folder at the project dir and below the folder where my docker-compose.yml file is. When I does it, the folder is just empty not showing any files.

e.g. before I used - ./:/mara and it bound to the folder where my docker-compose file is. But now, the folder is just empty.

I don't know the docker windows version I used before, so, I can't explain since when this issue occurs.

I tried to use relative paths and absolute paths but it does not work. But I can bind to folders below my project root. E.g. I can bind to /, /home, /home/myusername, /home/myusername/git, /home/myusername/git/user but not to , /home/myusername/git/user/my_project and below.

• [x] I have tried with the latest version of Docker Desktop
• [x] I have tried disabling enabled experimental features
• [ ] I have uploaded Diagnostics
• Diagnostics ID:

Actual behavior

The folder is empty in the docker container... the volume binding does not work.

Expected behavior

I would expect the paths to be mapped to the local drive folder as before.

Information

Please, help us understand the problem.

• Is it reproducible? Yes

• Is the problem new? Yes

• Did the problem appear with an update? Yes

• Windows Version: Windows 11

• Docker Desktop Version: Docker version 20.10.5+dfsg1, build 55c4c88

• WSL2 or Hyper-V backend? WSL2

• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

[2023-03-07T07:08:56.419654800Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[FAIL] DD0005: is the user in the docker-users group? The user name could not be found.
[PASS] DD0038: is the connection to Docker working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?

Please investigate the following 1 issue:

1 : The test: is the user in the docker-users group?
    Failed with: The user name could not be found.

The current user must be member of the docker-users group. Press the Win + R keys to open Run, type lusrmgr.msc into Run, followed by Enter to open Local Users and Groups.

Steps to reproduce the behavior

1. Create a docker-compose.yml file using a volume directing to - ./:/my_conatiner_dir
2. Start the container
3. check the content of folder /my_conatiner_dir in the container. It willl be empty.

[docker-robot[bot]]

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale