Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker refuses to shut down #14485

Open
IainMcCracken opened this issue Dec 14, 2024 · 3 comments
Open

Docker refuses to shut down #14485

IainMcCracken opened this issue Dec 14, 2024 · 3 comments

Comments

@IainMcCracken
Copy link

Description

When I select "Quit Docker Desktop" from the menu at the bottom of the Docker Destop window, it shows the "Turning off the Docker Engine..." page for a very long time, then returns to the regular list of containers screen.

At this point, it is dead. Containers do not open. The Desktop app cannot access the contents of volumes. Nothing works.

Windows Task Manager says that the docker desktop and docker backend tasks are still running.

The only way to get Docker back up and running again is to force all tasks with "docker" in the name to exit. Or reboot the machine.

Reproduce

  1. Run Docker Desktop from the Start menu, or by double-clicking the icon on the desktop.
  2. Select "Quit Docker Desktop" from the menu at the bottom of the window.

Expected behavior

"Quit Docker Desktop" should:

  1. Stop the Docker Engine
  2. Exit Docker Desktop

docker version

Client:
 Version:           27.4.0
 API version:       1.47
 Go version:        go1.22.10
 Git commit:        bde2b89
 Built:             Sat Dec  7 10:40:21 2024
 OS/Arch:           windows/amd64
 Context:           desktop-linux

Server: Docker Desktop 4.37.0 (178034)
 Engine:
  Version:          27.4.0
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.10
  Git commit:       92a8393
  Built:            Sat Dec  7 10:38:57 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.21
  GitCommit:        472731909fa34bd7bc9c087e4c27943f9835f111
 runc:
  Version:          1.1.13
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    27.4.0
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  ai: Ask Gordon - Docker Agent (Docker Inc.)
    Version:  v0.5.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-ai.exe
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.19.2-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.31.0-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.37
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.0
    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
  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.4.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.15.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 27.4.0
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 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: 472731909fa34bd7bc9c087e4c27943f9835f111
 runc version: v1.1.13-0-g58aa920
 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: 8
 Total Memory: 5.684GiB
 Name: docker-desktop
 ID: 1eb8afd9-cfef-4a4a-aaa2-2342b322d447
 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

Diagnostics ID

1895F3C5-FBAB-4EF2-B6D7-BB9852659B2D/20241214191646

Additional Info

I'm going go back to 4.36 which seems to work.

@rimelek
Copy link

rimelek commented Dec 14, 2024

In case it helps Docker, this is where we discussed it originally: https://forums.docker.com/t/new-bug-4-37-0-docker-desktop-refuses-to-shut-down/145478

We could not reproduce the issue with DD v4.37 and so far the only difference we saw is the hardware. Also quoting an error shared by @IainMcCracken on the forum:

I’m looking at the log files (AppData/Local/Docler/log/vm) and in 01-docker.log I see a slew of errors about device or resource busy, failed to remove cgroup.

But I checked now, and I have those error messages too without having any problem with quitting Docker Desktop

@IainMcCracken
Copy link
Author

Thanks, rimelek, for adding that info.

I am at a loss as to why 4.37 works just fine on my desktop, and not on my laptop, while 4.36 is fine on both machines.

@IainMcCracken
Copy link
Author

Update...

Version 4.37.1 just installed itself on my laptop and it shuts down just fine.

So, there was something about my laptop and 4.37.0 that was problematic. No idea what, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants