Operations hang after starting system prune
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 - 82040D1C-9491-46F7-A12E-B917B287132F ``` 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`
Posted by acdha on Jan 24, 2018, 6:34 PM
Tags
Related issues
- Some good points here, and I definitely hate the "unalive" movement but like someone else said, it has gone beyond self-censorship to in-...
- It’s hard to take the article seriously when there’s no real discussion about how consciousness is defined and it takes Anthropic’s views...
- you know what i hate?
- > I honestly do not understand why any average person would buy anything else than a macbook today.
- Codex App frequently freezes/stutters on Windows 11 Pro despite sufficient system resources
- Add "Basic" and "Standard" plans
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
ux (SaaS)
Some good points here, and I definitely hate the "unalive" movement but like someone else said, it has gone beyond self-censorship to in-...
It’s hard to take the article seriously when there’s no real discussion about how consciousness is defined and it takes Anthropic’s views...
you know what i hate?
> I honestly do not understand why any average person would buy anything else than a macbook today.
Codex App frequently freezes/stutters on Windows 11 Pro despite sufficient system resources
Add "Basic" and "Standard" plans
FEATURE: Multi-window support in Claude Code Desktop
Hi HN I built CookPal to solve a small but annoying problem for myself: I kept saving recipes from websites, TikTok, YouTube, and Instag...
Operations hang after starting system prune
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 - 82040D1C-9491-46F7-A12E-B917B287132F ``` 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`
Comments (0)
No comments yet. Start the discussion.