There was nothing there that really stood out, except for the reported System size: a whopping 87 GB. Out of ideas, I went to About This Mac (click on the Apple icon on the left side of the OS toolbar) and then to the Storage tab. I created storage pool and volumes as in the screenshot attached.

The folder where I store work stuff takes a modest 3 GB of disk space, much less than what I was expecting.ĭid I accidentally put something really big on Dropbox on another device that was synced to my MacBook Pro? Since I’m a programmer working at Konduto, a company that uses machine learning for fraud prevention and therefore works with very big files, I imagined a database dump or large CSV could be the cause. No pictures, no movies, no music (only Spotify) and no games. The thing is I only use my MacBook Pro for work purposes. I know that with a 120 GB SSD I’m definitely not a large landowner of disk space. MacOS has recently notified me that a system update would not be performed because I did not have 12 GB of free space in my disk. One of the lines in the Dockerfile calls ADD to expose the directory in the container, so the files can be copied to where they need to be.Docker for Mac causing disk space issues A disk space problem

I’m not sure if I’m using the tool incorrectly or what, but we have a git repository containing all of the source as well as a Dockerfile at the top level. I have checked, and I have plenty of free inodes and plenty of free space. During this copy procedure, I start seeing all kinds of ‘no space left on device’ errors, and the build fails. However, there is a section in the install procedure where a bunch of source code files (around 3gb of files) are copied to various places in the file system, including /dev/shm. The Dockerfile runs along nicely, installing nodejs, postgresql, and some other dependencies. Our installation procedure depends heavily on the directory structure of OpenSUSE, so I’m using OpenSUSE 13.1 as my base. It is possible to expand the root device by snapshotting and then building a new AMI against an expanded snapshot size, but for me the easy fix was to add a volume on the instance and then point. I’m using Docker both to automate this process as well as hopefully migrate away from OpenSUSE toward CentOS. It’s got all kinds of weird undocumented dependencies, and I’m trying to automate as much of this as I can.

We’ve got a large web application that’s a huge pain to install on a fresh machine. I’m pretty new to Docker, and I’ve been struggling with this issue for the past day or so.

Docker for mac no space left on device