Cannot bind a windows folder

zxln007 commented 1 year ago

[x] I have tried with the latest version of Docker Desktop
[x] I have tried disabling enabled experimental features
[x] I have uploaded Diagnostics
Diagnostics ID: D806F768-D4A7-4A3E-8F4F-FB1DD8C571FD/20230413070043

Actual behavior

i mount 5 folder in a container , 4 of them mounted successfully ,

but only one cannot mount . not always , about 10 percent .

a part of docker-compose.yml

    container_name: aaa
    image: aaa
    restart: always
    privileged: true
    ports:
      - "127.0.0.1:2001:2001"
    volumes:
       - /run/desktop/mnt/host/c/zxln007/backup:/backup
       - /run/desktop/mnt/host/c/zxln007/home/data:/data
       - /run/desktop/mnt/host/c/zxln007/opt/image:/headimage
       - /run/desktop/mnt/host/c/zxln007/etc/bp/meta/shared:/shared
       - /run/desktop/mnt/host/c/zxln007/home/data/dav/cards/collections/collection-root/root:/addressbook

Expected behavior

mount all folder successfully

Information

Windows Version: Windows 10 Pro internal version： 19045.2846
Docker Desktop Version: 4.18.0
WSL2 or Hyper-V backend? WSL2
Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No
Did the problem appear with an update? Maybe appear after exec wsl --update

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

[2023-04-13T07:03:38.088311200Z][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?
[FAIL] DD0002: does the bootloader have virtualization enabled? contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:39.172188800Z][com.docker.diagnose.exe][I] ipc.NewClient: ab903a74-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service
[2023-04-13T07:03:39.172188800Z][com.docker.diagnose.exe][I] (bba78cae) ab903a74-com.docker.diagnose C->S com.docker.service GET /hyperv/bootloader
[2023-04-13T07:03:39.172704200Z][com.docker.diagnose.exe][W] (bba78cae) ab903a74-com.docker.diagnose C<-S NoResponse GET /hyperv/bootloader (515.4µs): Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:39.172704200Z][com.docker.diagnose.exe][I] (bba78cae-1) ab903a74-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:39.173217200Z][com.docker.diagnose.exe][W] (bba78cae-1) ab903a74-com.docker.diagnose C<-S NoResponse GET /ping (513µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:40.174069200Z][com.docker.diagnose.exe][I] (bba78cae-2) ab903a74-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:40.174257500Z][com.docker.diagnose.exe][W] (bba78cae-2) ab903a74-com.docker.diagnose C<-S NoResponse GET /ping (188.3µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:41.187373000Z][com.docker.diagnose.exe][I] (bba78cae-3) ab903a74-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:41.187373000Z][com.docker.diagnose.exe][W] (bba78cae-3) ab903a74-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:42.189484800Z][com.docker.diagnose.exe][I] (bba78cae-4) ab903a74-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:42.191454600Z][com.docker.diagnose.exe][W] (bba78cae-4) ab903a74-com.docker.diagnose C<-S NoResponse GET /ping (1.823ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:43.196879500Z][com.docker.diagnose.exe][I] (bba78cae-5) ab903a74-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:43.197252400Z][com.docker.diagnose.exe][W] (bba78cae-5) ab903a74-com.docker.diagnose C<-S NoResponse GET /ping (372.9µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:44.207645900Z][com.docker.diagnose.exe][I] (bba78cae-6) ab903a74-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:44.208234000Z][com.docker.diagnose.exe][W] (bba78cae-6) ab903a74-com.docker.diagnose C<-S NoResponse GET /ping (527µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:45.221398300Z][com.docker.diagnose.exe][I] (bba78cae-7) ab903a74-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:45.221398300Z][com.docker.diagnose.exe][W] (bba78cae-7) ab903a74-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:46.233992700Z][com.docker.diagnose.exe][I] (bba78cae-8) ab903a74-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:46.234337800Z][com.docker.diagnose.exe][W] (bba78cae-8) ab903a74-com.docker.diagnose C<-S NoResponse GET /ping (345.1µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[FAIL] DD0022: is the Virtual Machine Platform Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:46.248532700Z][com.docker.diagnose.exe][I] ipc.NewClient: bfe45609-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service
[2023-04-13T07:03:46.248532700Z][com.docker.diagnose.exe][I] (c643e4da) bfe45609-com.docker.diagnose C->S com.docker.service POST /windowsfeatures/check: [VirtualMachinePlatform (Virtual Machine Platform)]
[2023-04-13T07:03:46.249532400Z][com.docker.diagnose.exe][W] (c643e4da) bfe45609-com.docker.diagnose C<-S NoResponse POST /windowsfeatures/check (999.7µs): Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:46.249532400Z][com.docker.diagnose.exe][I] (c643e4da-1) bfe45609-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:46.249532400Z][com.docker.diagnose.exe][W] (c643e4da-1) bfe45609-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:47.249575300Z][com.docker.diagnose.exe][I] (c643e4da-2) bfe45609-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:47.249755500Z][com.docker.diagnose.exe][W] (c643e4da-2) bfe45609-com.docker.diagnose C<-S NoResponse GET /ping (180.2µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:48.265708000Z][com.docker.diagnose.exe][I] (c643e4da-3) bfe45609-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:48.266703200Z][com.docker.diagnose.exe][W] (c643e4da-3) bfe45609-com.docker.diagnose C<-S NoResponse GET /ping (1.8379ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:49.274839800Z][com.docker.diagnose.exe][I] (c643e4da-4) bfe45609-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:49.276611200Z][com.docker.diagnose.exe][W] (c643e4da-4) bfe45609-com.docker.diagnose C<-S NoResponse GET /ping (1.7714ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:50.283327200Z][com.docker.diagnose.exe][I] (c643e4da-5) bfe45609-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:50.285141300Z][com.docker.diagnose.exe][W] (c643e4da-5) bfe45609-com.docker.diagnose C<-S NoResponse GET /ping (1.8141ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:51.296618400Z][com.docker.diagnose.exe][I] (c643e4da-6) bfe45609-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:51.296618400Z][com.docker.diagnose.exe][W] (c643e4da-6) bfe45609-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:52.297693900Z][com.docker.diagnose.exe][I] (c643e4da-7) bfe45609-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:52.297693900Z][com.docker.diagnose.exe][W] (c643e4da-7) bfe45609-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:53.311272800Z][com.docker.diagnose.exe][I] (c643e4da-8) bfe45609-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:53.311272800Z][com.docker.diagnose.exe][W] (c643e4da-8) bfe45609-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

[FAIL] DD0021: is the WSL 2 Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:53.313092100Z][com.docker.diagnose.exe][I] ipc.NewClient: 69926dfa-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service
[2023-04-13T07:03:53.313092100Z][com.docker.diagnose.exe][I] (a8961b1e) 69926dfa-com.docker.diagnose C->S com.docker.service POST /windowsfeatures/check: [Microsoft-Windows-Subsystem-Linux (Windows Subsystem for Linux)]
[2023-04-13T07:03:53.313092100Z][com.docker.diagnose.exe][W] (a8961b1e) 69926dfa-com.docker.diagnose C<-S NoResponse POST /windowsfeatures/check (0s): Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:53.313092100Z][com.docker.diagnose.exe][I] (a8961b1e-1) 69926dfa-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:53.314092900Z][com.docker.diagnose.exe][W] (a8961b1e-1) 69926dfa-com.docker.diagnose C<-S NoResponse GET /ping (1.0008ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:54.326143200Z][com.docker.diagnose.exe][I] (a8961b1e-2) 69926dfa-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:54.326143200Z][com.docker.diagnose.exe][W] (a8961b1e-2) 69926dfa-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:55.337696200Z][com.docker.diagnose.exe][I] (a8961b1e-3) 69926dfa-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:55.338733900Z][com.docker.diagnose.exe][W] (a8961b1e-3) 69926dfa-com.docker.diagnose C<-S NoResponse GET /ping (1.0377ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:56.347774900Z][com.docker.diagnose.exe][I] (a8961b1e-4) 69926dfa-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:56.347774900Z][com.docker.diagnose.exe][W] (a8961b1e-4) 69926dfa-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:57.358379000Z][com.docker.diagnose.exe][I] (a8961b1e-5) 69926dfa-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:57.358379000Z][com.docker.diagnose.exe][W] (a8961b1e-5) 69926dfa-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:58.359874200Z][com.docker.diagnose.exe][I] (a8961b1e-6) 69926dfa-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:58.359874200Z][com.docker.diagnose.exe][W] (a8961b1e-6) 69926dfa-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:03:59.374677700Z][com.docker.diagnose.exe][I] (a8961b1e-7) 69926dfa-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:03:59.375524900Z][com.docker.diagnose.exe][W] (a8961b1e-7) 69926dfa-com.docker.diagnose C<-S NoResponse GET /ping (847.2µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:04:00.388873900Z][com.docker.diagnose.exe][I] (a8961b1e-8) 69926dfa-com.docker.diagnose C->S com.docker.service GET /ping
[2023-04-13T07:04:00.389007200Z][com.docker.diagnose.exe][W] (a8961b1e-8) 69926dfa-com.docker.diagnose C<-S NoResponse GET /ping (133.3µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? [ 3801.041124] EXT4-fs error (device sdc): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal
[FAIL] DD0035: is the VM time synchronized? parsing time output: 2023-04-13T07:04:00+00:00: parsing time "2023-04-13T07:04:00+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"
[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?
[PASS] DD0005: is the user in the docker-users group?
[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?
[FAIL] DD0006: is the Docker Desktop Service responding? failed to ping com.docker.service with error: Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-04-13T07:04:03.541917800Z][com.docker.diagnose.exe][I] ipc.NewClient: 3f3d4581-diagnose -> \\.\pipe\dockerBackendV2 Service
[2023-04-13T07:04:03.542437500Z][com.docker.diagnose.exe][I] (e507135a) 3f3d4581-diagnose C->S Service GET /ping
[2023-04-13T07:04:03.542437500Z][com.docker.diagnose.exe][W] (e507135a) 3f3d4581-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[WARN] DD0002: does the bootloader have virtualization enabled? contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[WARN] DD0022: is the Virtual Machine Platform Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[WARN] DD0021: is the WSL 2 Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[WARN] DD0029: is the WSL 2 Linux filesystem corrupt? [ 3801.041124] EXT4-fs error (device sdc): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal
[WARN] DD0035: is the VM time synchronized? parsing time output: 2023-04-13T07:04:00+00:00: parsing time "2023-04-13T07:04:00+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"
[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?
[WARN] DD0032: do Docker networks overlap with host IPs? network bp-cicada has subnet 172.18.0.0/16 which overlaps with host IP 172.18.208.1

Please note the following 25 warnings:

1 : The check: does the bootloader have virtualization enabled?
    Produced the following warning: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled.
Run:
 bcdedit /set hypervisorlaunchtype auto

2 : The check: does the bootloader have virtualization enabled?
    Produced the following warning: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled.
Run:
 bcdedit /set hypervisorlaunchtype auto

3 : The check: is the Virtual Machine Platform Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

4 : The check: is the WSL 2 Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

5 : The check: is the Virtual Machine Platform Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

6 : The check: is the WSL 2 Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

7 : The check: is the Virtual Machine Platform Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

8 : The check: is the WSL 2 Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

9 : The check: is the Virtual Machine Platform Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

10 : The check: is the WSL 2 Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

11 : The check: is the Virtual Machine Platform Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

12 : The check: is the WSL 2 Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

13 : The check: is the Virtual Machine Platform Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

14 : The check: is the WSL 2 Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

15 : The check: is the WSL 2 Linux filesystem corrupt?
    Produced the following warning: [ 3801.041124] EXT4-fs error (device sdc): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal

If the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.
There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:
https://github.com/microsoft/WSL/issues/5895 .

Try running "wsl --shutdown" to stop your WSL Virtual Machine. When it restarts it will
run a filesystem check and hopefully fix the problem.

16 : The check: is the Virtual Machine Platform Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

17 : The check: is the WSL 2 Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

18 : The check: is the Virtual Machine Platform Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

19 : The check: is the WSL 2 Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

20 : The check: is the Virtual Machine Platform Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

21 : The check: is the WSL 2 Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

22 : The check: is the Virtual Machine Platform Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

23 : The check: is the WSL 2 Windows Feature enabled?
    Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

24 : The check: is the VM time synchronized?
    Produced the following warning: parsing time output: 2023-04-13T07:04:00+00:00: parsing time "2023-04-13T07:04:00+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"

The VM time must be in sync with the host, otherwise Docker Desktop will not work correctly.

Ensure you are using a modern WSL 2 kernel (see "wsl --update"). If this problem persists,
try manually synchronizing the VM clock with "sudo hwclock -s".

25 : The check: do Docker networks overlap with host IPs?
    Produced the following warning: network bp-cicada has subnet 172.18.0.0/16 which overlaps with host IP 172.18.208.1

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address

Please investigate the following 3 issues:

1 : The test: is the Virtual Machine Platform Windows Feature enabled?
    Failed with: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10

2 : The test: is the Docker Desktop Service responding?
    Failed with: failed to ping com.docker.service with error: Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Docker Desktop Service is needed to start the Docker engine. Open the list of Services and configure the Docker Desktop Service to start automatically.

3 : The test: does the bootloader have virtualization enabled?
    Failed with: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.

The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled.
Run:
 bcdedit /set hypervisorlaunchtype auto

Steps to reproduce the behavior

...
...

milas commented 1 year ago

From the diag, there are some cases where the mount is failing:

[2023-04-11T11:51:26.614977600Z][dockerd][I] time="2023-04-11T11:51:26.614278300Z" level=error msg="Handler for POST /v1.41/containers/257ba5c143acc5821718fb23728addf0bc4dc8775fea0bef3e4fc5bf58556575/start returned error: error while creating mount source path '/run/desktop/mnt/host/e/backup': mkdir /run/desktop/mnt/host/e: file exists"

That's on E:\ rather than C:\ as shown in your example -- is this different? Is E:\ a removable drive by chance?

One thing to note is that the 2x bind mount syntaxes vary in behavior in Docker:

short form (that you're using), e.g. -v /foo:/bar will create /foo on the host if it does not exist
long form will NOT create host path
type: bind source: /foo target: /bar

If you convert your volumes into the long syntax in Compose, does the issue go away? That will help us determine if there is an underlying race issue in Compose/Engine.

zxln007 commented 1 year ago

From the diag, there are some cases where the mount is failing:
[2023-04-11T11:51:26.614977600Z][dockerd][I] time="2023-04-11T11:51:26.614278300Z" level=error msg="Handler for POST /v1.41/containers/257ba5c143acc5821718fb23728addf0bc4dc8775fea0bef3e4fc5bf58556575/start returned error: error while creating mount source path '/run/desktop/mnt/host/e/backup': mkdir /run/desktop/mnt/host/e: file exists"
That's on E:\ rather than C:\ as shown in your example -- is this different? Is E:\ a removable drive by chance?

One thing to note is that the 2x bind mount syntaxes vary in behavior in Docker:

short form (that you're using), e.g. -v /foo:/bar will create /foo on the host if it does not exist

long form will NOT create host path
- type: bind
  source: /foo
  target: /bar
If you convert your volumes into the long syntax in Compose, does the issue go away? That will help us determine if there is an underlying race issue in Compose/Engine.

Sorry ! the compose file i copy wrong,

it should be /run/desktop/mnt/host/e/zxln007/backup:/backup

Yes you are right ,E:/ is a USB Disk.

i will try your comment , thank you very much @milas

zxln007 commented 1 year ago

I give up to mount the usb disk , i tried to mount the folder on the local disk.

but i still encountered the same problem. Mount failed !

after try many times , I found a law！

when i change the folder to a new folder like this：

/run/desktop/mnt/host/c/zxln007/file/backup:/mybackup

it works! the folder mounted successfully

when i restart the container , it mount failed again

it seems a new path could be mounted , and after restart container, it lose efficacy

why? thanks for your help @milas

docker / for-win