Docker Community Forums

Share and learn in the Docker community.

Docker for Mac is hosed after "no space left on device"

(Jamshid) #1

Expected behavior

I should be able to at least restart docker after running out of disk space.
Location of the docker server (virtual?) disk should be well documented.
If disk is fixed size or has a maximum size, it should be documented how to change that.
Note my Mac itself hasn’t run out of space – it has 60GB free.

Actual behavior

I can’t start docker after running out of disk space. Can’t figure out how to diagnose the problem further. Will try a pinata reset.


  • the output of:
    • pinata diagnose -u on OSX
      OS X: version 10.11.4 (build: 15E65) version v1.11.0-beta6
      Running diagnostic tests:
      Error docker ps: timeout after 10.00s
      Error docker ps: timeout after 10.00s
      Thread 6 killed on uncaught exception Misc.Failure
      [OK] Moby booted
      [OK] driver.amd64-linux
      [OK] vmnetd
      [OK] osxfs
      [OK] db
      [OK] slirp
      [OK] menubar
      [OK] environment
      [OK] Docker
      [OK] VT-x
      Error exec: nc -U /tmp/diagnose.socket > /tmp/20160405-224351/diagnostics.tar: exit 1
      Docker logs are being collected into /tmp/20160405-224351.tar.gz.
      Your unique id in bugsnag is: 8AEFDAE1-75EC-4A92-82ED-18B7FDF1C239

I see in
time=“2016-04-06T03:43:44.551626885Z” level=fatal msg="Error starting daemon: Error initializing network controller: error obtaining controller instance: listen unix /var/lib/docker/network/files/4e946963e54ad594382c7eff53cf245b07aa981dfaf35d94741e6f8494b4b525.sock: bind: no space left on device"
and I see this is 44GB

Steps to reproduce the behavior

  1. Build and run a lot of containers.

(Jamshid) #2

I never could figure out how to fix or diagnose. Nothing was output by “pinata restart --debug”. I ended up having to do a “Reset to Factory Defaults”.