title: gitlab-runner running out of space, with added disk drive
body: <p>I have a gitlab-runner (docker executor) that is building a large docker image using <code>docker build</code>. This is running out of space.</p>
  <p>To remedy this, I mounted an external disk (with adequate space) and created a partition. This can be found and accessed at <code>/run/media/&lt;user&gt;/STORAGE</code>. I created a directory here called <code>builds</code>, where I hope Gitlab-runner to build my docker images (using the new external disks space).</p>
  <p>Under the <code>[[runners]]</code> settings in <code>/etc/gitlab-runner/config.toml</code>, I have set <code>builds_dir = &quot;/run/media/&lt;user&gt;/STORAGE/builds&quot;</code>.</p>
  <p>The gitlab-runner logs suggest that the external disk is being used (<code>Initialized empty Git repository in /run/media/&lt;user&gt;/STORAGE/builds/&lt;user&gt;/&lt;repository-name&gt;/.git/</code>), but the build is still failing at the same stage and time (<code>no space left on device</code>), suggesting that the build itself is still being done on the old disk space.</p>
  <p>Have I understood the purpose of the <code>builds_dir</code> setting correctly? How do I get gitlab-runner to just use the new disk?</p>