search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.85k stars 287 forks source link

Docker Engine won't start, WSL issue even after shutdown. A6C12B26-BB63-4CF5-8072-6C34617A8E2C/20230508165529 #13472

Open mstrbstrd opened 1 year ago

mstrbstrd commented 1 year ago

Actual behavior

Expected behavior

Information

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

Steps to reproduce the behavior

  1. ...
  2. ...
ctalledo commented 1 year ago

Hi @mstrbstrd, thanks for filing the issue.

Per the diagnostic bundle you uploaded, there appears to be a problem with Docker Desktop's WSL integration service:

[2023-05-08T16:37:02.858005600Z][com.docker.backend.exe][E] WSLIntegrationService: start failed: starting added distros: 1 error occurred:
        * waiting for WSL integration for Ubuntu-18.04: waiting for WSL distro integration to become ready

The WSL integration service is a software agent that Docker Desktop runs on your WSL distros (e.g., Ubuntu-18.04) in order for Docker to be available from within the distro. For some reason the agent is not coming up, causing Docker Desktop to not work correctly. It's not clear why the agent fails to come up though.

As a work-around, try disabling Docker Desktop's WSL integration feature by editing the C:\Users\<USER_NAME>\AppData\Roaming\Docker\settings.json file:

"enableIntegrationWithDefaultWslDistro": false,
"integratedWslDistros": [],

Then start Docker Desktop and check if that enables it to start working properly.

In addition, check if your WSL distro is working correctly (e.g., wsl -d Ubuntu-18.04). If so, then try re-enabling WSL integration in Docker Deskop via the Dashboard's "Settings -> Resources -> WSL Integration" menu.

samuk190 commented 1 year ago

There is a memory leak issue with docker desktop since years ago. If your computer have not much ram available then maybe the memory leak will kick it faster and your docker will not even start.

Highly recommend switching to docker desktop hyper V but keep in mind this will sacrifice a part of your system resources all time and not use resources on demand as wsl2 integration was supposed to do.

Sadly we need to make this issue more known so the devs focus 100% on it.

ctalledo commented 1 year ago

There is a memory leak issue with docker desktop since years ago. If your computer have not much ram available then maybe the memory leak will kick it faster and your docker will not even start.

Highly recommend switching to docker desktop hyper V but keep in mind this will sacrifice a part of your system resources all time and not use resources on demand as wsl2 integration was supposed to do.

Sadly we need to make this issue more known so the devs focus 100% on it.

We are working on it, see this comment for more info.