search

docker / for-mac

Bug reports for Docker Desktop for Mac
https://www.docker.com/products/docker#/mac
2.44k stars 119 forks source link

Operations hang after starting system prune #2501

Open acdha opened 6 years ago

acdha commented 6 years ago

I ran docker system prune to clear out old dev images. That appears to have hung with no feedback: commands like docker ps hang and there's no UI indicating what might be the problem. There were periods where Hyperkit was 140% CPU but the running average is close to idle and disk I/O has fluctuated between modest (tens of operations per second) to idle.

It's possible that everything is working correctly but it'd be nice to know whether that's the case and whether I should just leave it running (after about 10 minutes) or if restarting it will be required.

Information

Docker for Mac: version: 17.12.0-ce-mac49 (d1778b704353fa5b79142a2055a2c11c8b48a653)
macOS: version 10.13.3 (build: 17D47)
logs: /tmp/82040D1C-9491-46F7-A12E-B917B287132F/20180124-132812.tar.gz
failure: docker ps failed: (Failure "docker ps: timeout after 10.00s")
[OK]     db.git
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     kubernetes
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     slirp
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[ERROR]  docker-cli
         docker ps failed
[OK]     menubar
[OK]     disk

Steps to reproduce the behavior

  1. docker system prune
  2. docker ps
gbajson-area22 commented 1 year ago

/remove-lifecycle stale

GrimzEcho commented 3 months ago

docker system prune --volume --all has been running for 45 minutes now without any feedback 

Docker Engine
Version:    27.1.2
Server:
 Containers: 5
  Running: 0
  Paused: 0
  Stopped: 5
 Images: 51
 Kernel Version: 6.1.0-23-amd64
 Operating System: Debian GNU/Linux 12 (bookworm)
harryvince commented 3 months ago

still present, no progress for pruning the builder cache either docker builder prune

this has been running for a few hours now

acdha commented 3 months ago

docker system prune --volume --all has been running for 45 minutes now without any feedback

As the original reporter, I feel I should note that I unsubscribed from this because I switched to Podman in 2021 and it's been so much better for performance, memory usage, and stability. Maybe your needs are more complicated than mine but at this point I'd have trouble believing that 2025 will be the year this issue is fixed.

dissolved commented 3 months ago

docker system prune --volume --all has been running for 45 minutes now without any feedback

As the original reporter, I feel I should note that I unsubscribed from this because I switched to Podman in 2021 and it's been so much better for performance, memory usage, and stability. Maybe your needs are more complicated than mine but at this point I'd have trouble believing that 2025 will be the year this issue is fixed.

Wow. Yeah, this probably will never be fixed. I will say this though, it does seem to affect a very small percentage of people. I worked at a company with ~40-50 developers all with similar toolchains as me and I was the only one impacted by this issue. When my computer was replaced (due to lifespan refresh, not for any other reason), I never had the issue again.