It then builds a second docker that executes a number of CMake/ninja install build runs on top of the source.

The host disk is 250Gig in total, while the dynamic linux partition is set tot 150 Gig max, leaving about 60 Gig free Gitlab-runner syncs the project source from an external submodule git, builds a docker (based on top of gcc:8 and dependencies) and pushes it to a repository. Guest OS: Ubuntu 19.10 x86_64 (kernel: 5.3.0-24-generic)ĭynamic VDI: 150Gig (max-use is ~ 70 Gig)Ī gitlab-runner is executing shell commands inside a Linux guest OS in a Virtual Box on top of the host OS (Windows 10). Profile: default Kernel Version: 4.9.58-xxxx-std-ipv6-64 Operating System: Debian GNU/Linux 9 (stretch) OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 7.625GiB Name: ns3306175 ID: 6YS2:EC6G:OSLT:4NB4:HMAQ:UQON:P6VO:WZJQ:ZCYO:BW3K:VZG5:AGW3 Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: Experimental: false Insecure Registries: 127.0.0.My issue is reproducible in a rather specific setup, so let's first give some context: Host OS: Windows 10 Docker info Containers: 15 Running: 12 Paused: 0 Stopped: 3 Images: 19 Server Version: 17.06.2-ce Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 6e23458c129b551d5c9871e5174f6b1b7f6d1170 runc version: 810190ceaa507aa2727d7ae6f4790c76ec150bd2 init version: 949e6fa Security Options: seccomp

Docker virtualbox increase disk size