Docker Community Forums

Share and learn in the Docker community.

Log filling up filesystem on Mac OS X


(Tory Long) #1

Expected behavior

Logs should rotate, or have a protection against filling up the root filesystem.

Actual behavior

Logs at the following fill up over time:

/Users//Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log/dmesg
/Users//Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log/docker.log

Reached 207 GB and 99 GB respectively.

Information

MBP:log username$ ls -la docker.log
-rw------- 1 username staff 99973256882 Jun 6 10:39 docker.log
MBP:log username$ ls -la dmesg
-rw-r–r-- 1 username staff 207398899712 Jun 6 10:34 dmesg

  • the output of:
    • pinata diagnose -u on OSX

Does not seem to run, due to full filesystem. Errors out with “diagnose: internal error, uncaught exception:
Misc.Failure”.

-  `DockerDebugInfo.ps1` using Powershell on Windows
  • a reproducible case if this is a bug, Dockerfiles FTW

Assume reproducible by filling logs.

  • page URL if this is a docs issue or the name of a man page
  • host distribution and version ( OSX 10.10.x, OSX 10.11.x, Windows, etc )

Host version: OSX 10.11.4

Steps to reproduce the behavior

  1. Logs filling due to warning messages.

(Bryce Ryan) #2

Hi, @wrlong.

The problem you’re experiencing may be resolved in one of our latest betas. We encountered a similar issue about a week ago, and resolved it. If you haven’t done so already, could you try updating to the latest beta, or at least Beta 13.1 or later. This should resolve the problem. If you’re on the latest beta, or upgrading docker for mac doesn’t resolve the problem with overfull logging, please let us know.

Thanks!

Bryce Ryan