Docker Community Forums

Share and learn in the Docker community.

Docker Daemon just wrote 324G of acpid.log


(Liveplandev) #1

Expected behavior

Not suddenly writing 400GB of log file

Actual behavior

Wrote 400GB of acpid.log

Information

pinata output (docker turned off)
OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[ERROR] docker-cli Connection refused (ECONNREFUSED) connecting to /var/run/docker.sock: check if service is running
[ERROR] docker-cli Connection refused (ECONNREFUSED) connecting to /Users/larry/Library/Containers/com.docker.docker/Data/s60: check if service is running
[OK] Moby booted
[ERROR] driver.amd64-linux Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running
[OK] driver.amd64-linux
[OK] vmnetd
[ERROR] osxfs com.docker.osxfs is not running
[OK] osxfs
[ERROR] db Connection refused (ECONNREFUSED) connecting to /Users/larry/Library/Containers/com.docker.docker/Data/s40: check if service is running
[ERROR] db com.docker.db is not running
[OK] db
[ERROR] slirp Connection refused (ECONNREFUSED) connecting to /Users/larry/Library/Containers/com.docker.docker/Data/s51: check if service is running
[ERROR] slirp com.docker.slirp is not running
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Error exec: cp -r β€œ/Users/larry/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log/acpid.log” β€œ/tmp/20160614-165943/moby/var/log/”: exit 1
Error exec: cp -r β€œ/Users/larry/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log/dmesg” β€œ/tmp/20160614-165943/moby/var/log/”: exit 1
Error exec: cp -r β€œ/Users/larry/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log/docker.log” β€œ/tmp/20160614-165943/moby/var/log/”: exit 1
Error exec: cp -r β€œ/Users/larry/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log/proxy-vsockd.log” β€œ/tmp/20160614-165943/moby/var/log/”: exit 1
Error exec: cp -r β€œ/Users/larry/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log/vsudd.log” β€œ/tmp/20160614-165943/moby/var/log/”: exit 1
Error exec: echo β€œ00000003.0000f3a6” | nc -U /Users/larry/Library/Containers/com.docker.docker/Data/@connect > /tmp/20160614-165943/diagnostics.tar: exit 1
Docker logs are being collected into /tmp/20160614-165943.tar.gz
Most specific failure is: com.docker.slirp is not running
Your unique id is: 42AD6900-7D1B-42C5-962D-E7F7AC3C6780
Please quote this in all correspondence.

Larrys-MacBook-Pro:log larry$ pwd
/Users/larry/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log
Larrys-MacBook-Pro:log larry$ du -sh *
324G	acpid.log
 40G	dmesg
 13G	docker.log
128K	messages
556K	messages.0
728K	proxy-vsockd.log
6.4G	vsudd.log
  0B	wtmp

Sample of the head and tail of the log 324G log file

Larrys-MacBook-Pro:log larry$ tail acpid.log
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/000Larrys-MacBook-Pro:log larry$ head acpid.log
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080
acpid: PWRF/00000080

Steps to reproduce the behavior

Ran docker for mac in the background for several weeks. Launched containers. Turned laptop on and off. Started it in various configurations; plugged in, unplugged, connected to displayport etc.

Turned docker off prior to running pinata since I do not wish to spam you w/ Gigabytes of compressed log file.

pinata output after clearing acpid.log

OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160614-170634.tar.gz
Most specific failure is: No error was detected
Your unique id is: 42AD6900-7D1B-42C5-962D-E7F7AC3C6780
Please quote this in all correspondence.

Hope that helps.