This behavior is only happening when attempting to run apt-get in a container using a mounted volume.
Otherwise apt-get install shouldn’t fail. I’m not sure what to look at.
Actual behavior
Receive the following error:
apt-get update -yqq
E: Unable to determine file size for fd 11 - fstat (2: No such file or directory)
Information
pinata diagnose -u on OSX
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta6
Running diagnostic tests:
[OK] docker-cli
[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/20160407-112050.tar.gz.
Your unique id in bugsnag is: 4C656227-B6CE-4149-8C4A-5A26C86E3445
Please quote this in all correspondence.
Steps to reproduce
Start a container with a volume mounted. I was using a docker-compose.yml definition.
Thanks for reporting this. We are aware of this issue which is due to apt-get's temporary file behavior which we do not correctly support. The work-around is to refrain from mounting host directories onto /tmp in apt-based distro containers. Do you continue to experience the issue when /tmp isn’t a bind mount?
I hope that in the next beta or two we will ship a fix for this.
Thanks for your participation in the Docker for Mac Beta!
Apparently not, I spent days troubleshooting this. Changed from mounting /tmp to something else and magically works now. As a docker newbie this was extremely frustrating experience. Glad I cam across this thread. Good luck to the next!