Before you chastise me for having a 12 GB image, know that it's the only way we can handle this specific scenario and still automate the build process. When I'm done with this project, I'll put myself in timeout - I promise.
Now, I'm working on a project with Opsworks and I need to pull down that very large image I mentioned. However, unless we use the AWS console, we can't change the size of the root volume on the EC2 instance in Opsworks. So, I mount a 50 GB volume at /var/lib/docker/ at startup. However, the Docker API is still saying that I'm running out of disk space (50 GB is much more than is necessary) during the image extraction. I'm guessing that docker is storing these temporary files somewhere other than in /var/lib/docker/ but for the life of me, I can't figure out where.
Hell, if someone can come up with a way to increase the root volume size of an Opsworks EC2 instance without creating a custom image, that would be nice too.
Any help would be appreciated.
By default, Docker will use /var/lib/docker/tmp for it's temporary directory. This can be overridden with the DOCKER_TMP environment variable for the docker daemon.