for-win icon indicating copy to clipboard operation
for-win copied to clipboard

Docker Desktop: WSL Distro Terminated Abruptly, running wsl-bootstrap: exit status 1

Open rfay opened this issue 1 year ago • 25 comments

Description

This failure happens almost daily on our DDEV Docker Desktop tests running in WSL2 using Docker Desktop. We have to restart DD or restart the machine (sometimes easier)

Docker Desktop: WSL Distro Terminated Abruptly, running wsl-bootstrap: exit status 1

image

This has been going on for months on both of our Docker Desktop for Windows machines, I've followed related issues, now making my own.

Reproduce

Run a lot of automated tests.

Expected behavior

Don't crash daily

docker version

PS C:\Users\testbot> docker version
Client:
 Version:           27.2.0
 API version:       1.47
 Go version:        go1.21.13
 Git commit:        3ab4256
 Built:             Tue Aug 27 14:17:17 2024
 OS/Arch:           windows/amd64
 Context:           desktop-linux

Server: Docker Desktop 4.34.2 (167172)
 Engine:
  Version:          27.2.0
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.21.13
  Git commit:       3ab5c7d
  Built:            Tue Aug 27 14:15:15 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.20
  GitCommit:        8fc6bcff51318944179630522a095cc9dbf9f353
 runc:
  Version:          1.1.13
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0

docker info

PS C:\Users\testbot> docker info
Client:
 Version:    27.2.0
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.2-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.2-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.34
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.15
    Path:     C:\Program Files\Docker\cli-plugins\docker-desktop.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.25
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.13.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
 Containers: 3
  Running: 3
  Paused: 0
  Stopped: 0
 Images: 32
 Server Version: 27.2.0
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 nvidia runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8fc6bcff51318944179630522a095cc9dbf9f353
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.15.153.1-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 11.69GiB
 Name: docker-desktop
 ID: 4c44aaf4-ff4c-4f21-98b1-295623742bb6
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=npipe://\\.\pipe\docker_cli
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile

Diagnostics ID

714965AA-305C-4811-B395-B1F87D1BCF18/20240923073255

Additional Info

This really is daily.

rfay avatar Sep 23 '24 07:09 rfay

Also having this in the past week

CaptainGlac1er avatar Sep 27 '24 19:09 CaptainGlac1er

Also started happening to me this past week. I reinstalled docker and it still happens

Kris-Pelteshki avatar Oct 06 '24 16:10 Kris-Pelteshki

Same for me. It started after the update to 4.34.3 (170107)

cvjjm avatar Oct 30 '24 14:10 cvjjm

+1

Docker 4.35.1 (173168), Win11 24H2 26100.2033

sambetts avatar Nov 07 '24 11:11 sambetts

starting to got this also at 4.35.1

WSL version: 2.3.26.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.2161

Image

damadorPL avatar Nov 12 '24 20:11 damadorPL

and now pull get

failed to extract layer sha256:4a8749d3d70bf42a1bab5ef1f85e81004553cdf9f28e7852d21acd0f227d608f: NotFound: failed to get reader from content store: blob sha256:4b280fd64312dfa90bb5e8de0b0d1a24e46886e3afe5938bfbfb9f3f08b85561 expected at /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/4b280fd64312dfa90bb5e8de0b0d1a24e46886e3afe5938bfbfb9f3f08b85561: blob not found: not found

damadorPL avatar Nov 12 '24 20:11 damadorPL

Any updates regarding this?

Docker Desktop version:

Version 4.34.1 (166053)

docker -v
Docker version 27.2.0, build 3ab4256
wsl -v
WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4317

meisbokai avatar Nov 13 '24 06:11 meisbokai

+1

Martin-Molinero avatar Nov 13 '24 13:11 Martin-Molinero

Here's another diagnostics ID of this issue: D86F43FB-C295-4947-AB51-5C3E0C03041A/20241113184124

mattico avatar Nov 13 '24 18:11 mattico

A796B5D0-FD09-42BA-9294-E0D4411EB028/20241119050639

CAPCOMIN avatar Nov 19 '24 05:11 CAPCOMIN

+1

Upd. : wsl --shutdown and restarting Docker Desktop solved the issue for now. It's working but I don't know if I should expect any errors

Upd. 2 : Ran some containers and reloaded PC several times. All good, data is persistent. Hope it helps you

17Sergey avatar Dec 01 '24 10:12 17Sergey

Having the same issue. Diagnostics ID: A61B2EE8-1B63-4C1A-A581-F207F73D5392/20241202073128

tlgDJPorv avatar Dec 02 '24 07:12 tlgDJPorv

Same issue, tho the wsl shutdown does nothing to resolve this issue. Diagnostic ID: D089C4CA-6652-4AC3-A093-BE7BCF18DCBB/20241204132924

Versions: Docker: 27.3.1 (docker -v) Docker Desktop: 4.36.0 (seen in UI) WSL : 2.3.24.0 (wsl -v) Noyau : 5.15.153.1-2 (wsl -v) WSLg : 1.0.65 (wsl -v) MSRDC : 1.2.5620 (wsl -v) Direct3D : 1.611.1-81528511 (wsl -v) DXCore : 10.0.26100.1-240331-1435.ge-release (wsl -v) Windows : 10.0.22631.4541 (wsl -v)

ibaraki-douji avatar Dec 04 '24 13:12 ibaraki-douji

Same problem here 1AA9D85F-C996-41FC-845E-C1C5B8A8C817/20250120130304

cvjjm avatar Jan 20 '25 13:01 cvjjm

Same issue and wsl shutdown did not help at all. Diagnostic ID: 88FA8625-A9CA-446D-87B8-0B659EA58B3A/20250124230347 Windows 11 23H2 (OS Build 22631.4751) Docker Desktop: 4.37.1 (178610) Docker version 27.4.0, build bde2b89

WSL version: 2.3.26.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.22631.4751

NoFace33 avatar Jan 24 '25 23:01 NoFace33

I am still experiencing this regularly. Very annoying.

cvjjm avatar Feb 14 '25 07:02 cvjjm

same here, and it's cuased by my WSL unexpected random termination, haven't found the problem yet

thinszx avatar Feb 14 '25 08:02 thinszx

I have the same issue too. It started happening recently. No real explanation but here are the details - pretty much the same as everyone esle so I'm surprised there has been no response.

Docker Desktop - WSL distro terminated abruptly A WSL distro that Docker Desktop relies on has exited unexpectedly. This usually happens as a result of an external entity terminating WSL (e.g. running wsl --shutdown). Restart Docker Desktop. If the issue persists,

running wsl-bootstrap: exit status 1

D5A7B8C9-6D28-4938-8FF4-E7C6235EFF93/20250214145840

Selecting restart from the diagnostice dialog does not restart the GUI but dosker is running as I can use the command line

I have also found Docker desktop to be unreliable when restarting from hibernation. The symptoms are that the GUI will not display but DOcker seems to be running but very slowly. I have to close from task manager and sometimes that doesn't work so need to reboot which can be incredibly inconvenient.

I'm using Win 11 pro version: 10.0.26100 build 26100 The laption is Dell XPS 15 9530 32 GB ram

OldGitHubber avatar Feb 14 '25 15:02 OldGitHubber

Here are a few more symptoms:

  1. when this happens I usually but not always get the error message in the original post, sometimes Docker Desktop just gets stuck and displays:

Image

In this case hitting retry does not do anything. 2. I always see something like time="2025-02-17T09:06:21+01:00" level=error msg="error waiting for container: unexpected EOF" on the console of running containers and then then console exits 3. I see no error messages on running wls consoles and the wls consoles keep working normally. 4. When I then do wsl --shutdown, I get the Docker Desktop - WSL distro terminated abruptly running wsl-bootstrap: exit status 1 error message. 5. After clicking "Restart" Docker Desktop shows the container list again and I can start containers again.

cvjjm avatar Feb 17 '25 12:02 cvjjm

Same problem with the Diagnostic ID: FEE5D795-CF02-417F-83A4-D97BE6F58549/20250219090034

jmrodriguezc avatar Feb 19 '25 09:02 jmrodriguezc

+1 docker v4.3.9 on windows 11 24H2

pigletfly avatar Mar 26 '25 01:03 pigletfly

+1 another diagnostic ID: 54760ACF-AB23-4400-A478-85BC8D8DA446/20250326034805

benitogf avatar Mar 26 '25 03:03 benitogf

+1 This problem is also happening on my end, 8097CDBF-07E9-4CE8-A940-A70B82DA2E69/20250326174439

wStobaugh avatar Mar 26 '25 17:03 wStobaugh

我也有这个问题,我们是部署在无人监管的环境下的,这样报错,会导致服务不运行,很麻烦

tianlongyang-bot avatar Mar 27 '25 02:03 tianlongyang-bot

Disabling Integration with additional distros in Docker Desktop settings helped me resolve this. docker command is still available inside my WSL distro.

turbcool avatar Mar 27 '25 07:03 turbcool

Wanted to add my voice to this as well, as I believe I'm experiencing the same issue - in my case, the WSL error seems to be brought about by visual studio building a container via buildx.

Diagnostics:

  • After shutdown after error: F1CE5D41-5E28-464C-AB86-ED46CD6A5D93/20250505130256 (uploaded)
  • After starting up fresh: F1CE5D41-5E28-464C-AB86-ED46CD6A5D93/20250505130416 (uploaded)
  • While showing the error (took 14m to generate): F1CE5D41-5E28-464C-AB86-ED46CD6A5D93/20250505130714 (uploaded)

I have disabled integration with other distros:

Image

On almost every build attempt, I see the same error reported above:

Image

❌ It is not fixed by running wsl --shutdown and restarting Docker Desktop ❌ It is not fixed by netsh winsock reset and restarting the PC. ❌ Not resolved by running Docker Desktop as administrator ❓ It typically doesn't work, but will occasionally (1/100 times?) work, and I cannot see what the difference is in those cases (waiting for it to happen again so I can capture diagnostics)

Expand to see the Results of "docker info"
Client:
 Version:    28.1.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  ai: Docker AI Agent - Ask Gordon (Docker Inc.)
    Version:  v1.1.7
    Path:     C:\Program Files\Docker\cli-plugins\docker-ai.exe
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.23.0-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  cloud: Docker Cloud (Docker Inc.)
    Version:  v0.3.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-cloud.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.35.1-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.38
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Docker Inc.)
    Version:  v0.1.8
    Path:     C:\Program Files\Docker\cli-plugins\docker-desktop.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  mcp: Docker MCP Plugin (Docker Inc.)
    Version:  dev
    Path:     C:\Program Files\Docker\cli-plugins\docker-mcp.exe
  model: Docker Model Runner (Docker Inc.)
    Version:  v0.1.11
    Path:     C:\Program Files\Docker\cli-plugins\docker-model.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.17.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe
WARNING: Plugin "C:\\Users\\SeanK\\.docker\\cli-plugins\\docker-feedback.exe" is not valid: failed to fetch metadata: fork/exec C:\Users\SeanK\.docker\cli-plugins\docker-feedback.exe: The system cannot find the file specified.

Server:
 Containers: 18
  Running: 0
  Paused: 0
  Stopped: 18
 Images: 30
 Server Version: 28.1.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 nvidia runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 05044ec0a9a75232cad458027ca83437aae3f4da
 runc version: v1.2.5-0-g59923ef
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.15.167.4-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 32
 Total Memory: 31.22GiB
 Name: docker-desktop
 ID: 9d0312f9-7b41-492e-8c94-6a6349e71150
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=npipe://\\.\pipe\docker_cli
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  ::1/128
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: DOCKER_INSECURE_NO_IPTABLES_RAW is set
WARNING: daemon is not using the default seccomp profile

SeanKilleen avatar May 05 '25 14:05 SeanKilleen

Same error. It's simply annoying

Image

juanchavezlive avatar May 06 '25 13:05 juanchavezlive

An update -- for my use case, I think a WSL upgrade may be what fixed it.

My WSL release was 2.4.13, the latest stable -- however, I saw some other docker desktop issues were fixed in the latest WSL preview release.

Since I was totally broken anyway, I figured -- might as well try the preview. 😆

I downloaded the installer for WSL v2.5.6 via https://github.com/microsoft/WSL/releases/tag/2.5.6 and installed it.

All issues resolved, Docker desktop works as expected, have had zero issues since (though it's only been a few hours).

I'm back up and running again and I hope this will help someone else get back up and running again (as long as you're OK installing a preview release).

SeanKilleen avatar May 15 '25 15:05 SeanKilleen

An update -- for my use case, I think a WSL upgrade may be what fixed it.

My WSL release was 2.4.13, the latest stable -- however, I saw some other docker desktop issues were fixed in the latest WSL preview release.

Since I was totally broken anyway, I figured -- might as well try the preview. 😆

I downloaded the installer for WSL v2.5.6 via https://github.com/microsoft/WSL/releases/tag/2.5.6 and installed it.

All issues resolved, Docker desktop works as expected, have had zero issues since (though it's only been a few hours).

I'm back up and running again and I hope this will help someone else get back up and running again (as long as you're OK installing a preview release).

This actually worked for me. I simply re-downloaded WSL and Ubuntu, then uninstalled and reinstalled Docker. Thanks a lot.

denda0duong avatar May 23 '25 20:05 denda0duong

This problem is still happening on my end, diagnostics ID: 88FA8625-A9CA-446D-87B8-0B659EA58B3A/20250527222507

NoFace33 avatar May 27 '25 22:05 NoFace33