Closed wwhurley closed 3 years ago
This did not occur for me until after installing vscode server and building a few images. This does not affect volume mounts when mounting from the windows fs, only from within WSL
I'm having the exact same issue.
My environment is : Windows 10, 1909 Build 18363.1049 Docker Desktop 2.3.5.1 (47433), Engine 19.03.13-beta2
I seem to have plenty of space on my device:
$ df -h /tmp/docker-desktop/shadowing-mounts/bb6ba5242a965074f76012000d2a2a131b0f513fce6e5c8d2e64b41a99e86dea
Filesystem Size Used Avail Use% Mounted on
/dev/sdd 251G 7.2G 232G 3% /
⚠ Holy smokes, do not sudo rm -rf /tmp/docker-desktop/
... It totally destroyed my WSL environment
I ran wsl --unregister docker-desktop-data
and wsl --unregister docker-desktop
and confirmed there were no errors starting wsl with dmesg -T
. After that I started docker-for-win and waited until those two images were running. Here is the output for dmesg
Most relevant looking section
[Mon Aug 31 11:03:13 2020] init: (2) ERROR: UtilCreateProcessAndWait:474: /bin/mount failed with 2
[Mon Aug 31 11:03:13 2020] init: (1) ERROR: UtilCreateProcessAndWait:489: /bin/mount failed with status 0x
[Mon Aug 31 11:03:13 2020] ff00
[Mon Aug 31 11:03:13 2020] init: (1) ERROR: ConfigMountFsTab:2077: Processing fstab with mount -a failed.
[Mon Aug 31 11:03:13 2020] init: (3) ERROR: UtilCreateProcessAndWait:474: /bin/mount failed with 2
[Mon Aug 31 11:03:13 2020] init: (1) ERROR: UtilCreateProcessAndWait:489: /bin/mount failed with status 0x
[Mon Aug 31 11:03:13 2020] ff00
[Mon Aug 31 11:03:13 2020] init: (1) ERROR: MountPlan9:478: mount cache=mmap,noatime,trans=fd,rfdno=8,wfdno=8,msize=65536,aname=drvfs;path=C:\;uid=0;gid=0;symlinkroot=/mnt/
[Mon Aug 31 11:03:13 2020] failed 2
[Mon Aug 31 11:03:13 2020] init: (1) ERROR: UpdateTimezone:97: Asia/Tokyo timezone not found. Is the tzdata package installed?
I'm having the exact same issue too. Also I see the same errors in dmesg when booting up.
My environment is : Windows 10, 1903 Build 18362.1049 Docker Desktop 2.3.6.0, Engine 19.03.13-beta2
Fixed for me in edge 2.3.6.1
Great. Fixed for me in edger 2.3.6.2. Thanks 👍
I'm having the exact same issue too. Also I see the same errors in dmesg when booting up.
My environment is : Windows 10, 1903 Build 18362.1049 Docker Desktop 2.3.6.0, Engine 19.03.13-beta2
Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
comment.
Stale issues will be closed after an additional 30 days of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked
Expected behavior
Launch Docker container with volume mounted, for example
docker run --rm -it -v /tmp/test/:/test alpine sh
Actual behavior
Docker container fails with the following message:
docker: Error response from daemon: mounting / to /tmp/docker-desktop/shadowing-mounts/abac646bc3d6076b3e0f0186c13b917b3ab78993ca80a2aaceacac3c911d9369: no space left on device.
Information
Steps to reproduce the behavior
docker run --rm -it -v /tmp/test/:/test alpine sh