Repository navigation
Stopping Docker Desktop doesn't terminate docker-desktop-data WSL2 distro #13443
Description
- I have tried with the latest version of Docker Desktop
- I have tried disabling enabled experimental features
- I have uploaded Diagnostics
- Diagnostics ID:
Actual behavior
After about a minute from stopping Docker Desktop the WSL2 disrto docker-desktop-data is still running while docker-desktop distro terminated
Expected behavior
Both distro docker-desktop and docker-desktop-data terminated shortly after quitting Docker Desktop
Information
- Windows Version: 10.0.22621.1555
- Docker Desktop Version: 4.18.0, 4.19.0
- WSL2 or Hyper-V backend? WSL2 version 1.2.5.0 Kernel version: 5.15.90.1
- 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
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[SKIP] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[SKIP] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[SKIP] 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?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? [ 4.090834] EXT4-fs error (device sdc): ext4_put_super:1188: comm weston: Couldn't clean up the journal
[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?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0038: is the connection to Docker working?
[FAIL] DD0014: are the backend processes running? 1 error occurred:
* com.docker.vpnkit.exe is not running
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[FAIL] DD0009: is the vpnkit API responding? open \.\pipe\dockerVpnKitDiagnostics: The system cannot find the file specified.
[PASS] DD0010: is the Docker API proxy responding?
[SKIP] 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?
[WARN] DD0029: is the WSL 2 Linux filesystem corrupt? [ 4.090834] EXT4-fs error (device sdc): ext4_put_super:1188: comm weston: Couldn't clean up the journal
[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 note the following 1 warning:
1 : The check: is the WSL 2 Linux filesystem corrupt?
Produced the following warning: [ 4.090834] EXT4-fs error (device sdc): ext4_put_super:1188: comm weston: 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:
microsoft/WSL#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.
Please investigate the following 1 issue:
1 : The test: is the WSL 2 Linux filesystem corrupt?
Failed with: [ 4.090834] EXT4-fs error (device sdc): ext4_put_super:1188: comm weston: 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:
microsoft/WSL#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.
Steps to reproduce the behavior
Resetting to factory settings doesn't resolve the issue.
The issue was reproduced on two independent workstations,
- Start Docker Desktop
- Stop Docker Desktop
- After about a minute from stopping Docker Desktop application check for running wsl2 distros
wsl -l -v - Confirm that
docker-desktop-datadistro is still running, whiledocker-desktopdistro is stopped.
Activity
[-]Stopping Docker Desktop doesn't stop running docker-desktop-data WSL2 distro[/-][+]Stopping Docker Desktop doesn't terminate docker-desktop-data WSL2 distro[/+]MihaelaStoica commentedon May 3, 2023
@alexeyvarganov Does the
docker-desktop-datadistro get stopped eventually, say after 2-3 minutes?adamjseitz commentedon May 3, 2023
I am not the original reporter, but I am experiencing this as well. It does not ever seem to get stopped for me.
alexeyvarganov commentedon May 5, 2023
The
docker-desktop-datadistro does not seem to stop at all based on some of my measurements - it continues to run indefinitely until I shutdown wslSynapseScribe commentedon May 17, 2023
same for me on win 11. eating 8 GB RAM even if i quit docker desktop from tray. i use WSL manager to stop docker-desktop-data and free the 8GB held by the VmmemWSL process (it takes a minute for it to end)
DuaRobin commentedon Jun 8, 2023
Same issue for me as well. After a couple min docker-desktop stops automatically, but after several min too docker-desktop-data doesn't stop. had to manually terminate thru
wsl --shutdown@fusionneur I did however manage to add a limit to RAM Usage (4GB) thru .wslconfig.
changetol8 commentedon Jun 9, 2023
I had the same issue on docker desktop 4.20.1 on windows 11. Need run
wsl --shutdownto terminate VmmemWSL processwohenbushuang commentedon Sep 18, 2023
same on win 10
MrMarvel commentedon Feb 1, 2024
Docker Desktop 4.27.0
Docker version 25.0.1
Windows 10
WSL: 2.0.14.0
Same here
~4GB is used
MrMarvel commentedon Feb 1, 2024
But on Docker Desktop 4.25.1 (128006)
wsl closes fine.
rmenai commentedon Feb 20, 2024
I'm also experiencing this issue.
jtvrdon commentedon Feb 25, 2024
For me it's the same. After quitting docker desktop:
docker-desktopanddocker-desktop-dataare still running in WSLdocker-desktopanddocker-desktop-datain WSL manually doesn't end VmmemWSL process (still 3G RAM usage)Docker Desktop v4.27.2
Docker Engine v25.0.3
Windows 11
WSL version: 2.0.9.0
D1lsh0D commentedon Mar 11, 2024
Same problem on Docker Desktop v4.28.0, Windows 11, WSL v2.0.14.0
Had to manually shutdown in terminal
MrMarvel commentedon Mar 18, 2024
Why devs have not already check this issue?
I have to sit on 4.25.1 because of this behavior
Adamou02 commentedon Mar 30, 2024
Same issue, pls fix it.
Have to manually do
wsl --shutdownto stop docker-desktop-data and docker-desktopnicolassimoncini commentedon Apr 7, 2024
Same here with Docker Desktop v4.28.0, Windows 10 22H2, WSL v2.1.5.0 😞
I manually stopped the images (
wsl -t <image>) and vmmemwsl just stopped after a few secconds.MihaelaStoica commentedon Apr 9, 2024
Hey everyone, we fixed the issue in Docker Desktop 4.29, please give it a try. I'm closing this ticket, but if you encounter the same again, please let us know.
Adamou02 commentedon Apr 9, 2024
Can you show me the pr pls. Just to analyze the solution.