title: Docker Machine: No space left on device
body: <p>I'm trying to set up Docker Machine with Docker Compose.</p>
  
  <p><strong>Scenario 1 (without Docker Machine)</strong><br>
  If I run <code>docker-compose up -d</code> without Docker Machine, it creates my 3 linked containers as intented (nginx+mongodb+nodejs).</p>
  
  <p><strong>Scenario 2 (with Docker Machine)</strong><br>
  Then I create a VM using Docker Machine and tell Docker to talk to that machine with <code>eval $(docker-machine env streambacker-dev)</code>.</p>
  
  <p>At this point, if I ssh to my docker machine and run <code>df -h</code>, I get:  </p>
  
  <p><img src="https://imgur.com/K4SoPTC.png" alt="docker machine df -h"></p>
  
  <p>If I then run <code>docker-compose up -d</code>, I get a <a href="https://imgur.com/ROS74NF" rel="noreferrer">"no space left on device" error</a> while downloading the last container.</p>
  
  <p>"tmpfs" seems to be indeed a bit full after that:</p>
  
  <p><img src="https://imgur.com/KHcOqIX.png" alt="docker machine df -h"></p>
  
  <p>Checking the <strong>--virtualbox-disk-size</strong> option shows that it defaults to 20000 MB, which I think is what we can see as "/dev/sda1" on both pictures. So why are containers filling up "tmpfs" n and what exactly is "tmpfs"? Is is a temporary download directory? <strong>How can I create more space for my containers?</strong></p>
  
  <p>Thanks!</p>
  
  <p>For information, I'm using <em>Docker Machine 0.4.0-rc2</em> and <em>Docker Compose 1.3.2</em>.</p>