ERROR: Preparation failed: write /var/lib/docker/tmp/GetImageBlob : no space left on device
Summary
Runner can't execute (new) jobs that require a new Docker image because there is no space left on the disk (diskspace). It is not a solution to add more and more disk space.
Expected behavior
The runner should delete unused (not frequently used) images or other files not needed frequently.
I'm aware of a separate tool (GitLab Runner Docker Cleanup), that could help with this. But I expect this from the gitlab-ci-multi-runner itself. Additionally I should not be required to bother with the configuration of that tool, because it seems to be inefficient (gitlab-runner-docker-cleanup#6). There was also a discussion on making it opt-out instead of opt-in (gitlab-runner-docker-cleanup#1 (closed)).
Relevant logs and/or screenshots
Running with gitlab-ci-multi-runner 1.11.1 (a67a225)
on
Using Docker executor with image ...
Pulling docker image ...
ERROR: Preparation failed: write /var/lib/docker/tmp/GetImageBlob: no space left on device
Will be retried in 3s ...
Using Docker executor with image ...
Pulling docker image ...
ERROR: Preparation failed: write /var/lib/docker/tmp/GetImageBlob: no space left on device
Will be retried in 3s ...
Using Docker executor with image ...
Pulling docker image ...
ERROR: Preparation failed: write /var/lib/docker/tmp/GetImageBlob: no space left on device
Will be retried in 3s ...
Environment description
Server Version: 17.03.0-ce
Kernel Version: 4.4.0-64-generic
Operating System: Ubuntu 16.04.2 LTS
Architecture: x86_64
Disk Size 63 GB
Used GitLab Runner version
Version: 1.11.1
Git revision: a67a225
Git branch: 1-11-stable
GO version: go1.7.5
Built: Fri, 03 Mar 2017 12:35:58 +0000
OS/Arch: linux/amd64
Edited by 🤖 GitLab Bot 🤖