I’ve added the following line to a rather simple gitlab-ci.yaml fil
image: ${CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX}/python:3.10
But I get the error
Running with gitlab-runner 15.11.0 (436955cb)
on docker-runner Uz5x5rch, system ID: r_YBpnILRXCEuA
Preparing the "docker" executor
Using Docker executor with image ubuntu-22.04.myguest.virtualbox.org:80/gitlab-instance-af848a70/dependency_proxy/containers/python:3.10 ...
Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image ubuntu-22.04.myguest.virtualbox.org:80/gitlab-instance-af848a70/dependency_proxy/containers/python:3.10 ...
WARNING: Failed to pull image with policy "always": expected HTTP 206 from byte range request (manager.go:237:172s)
ERROR: Job failed: failed to pull image "ubuntu-22.04.myguest.virtualbox.org:80/gitlab-instance-af848a70/dependency_proxy/containers/python:3.10" with specified policies [always]: expected HTTP 206 from byte range request (manager.go:237:172s)
The runner is a locally hosted docker image.
Is there some additional configuration that I require?
Could this be an out of disk memory error?
Here is the disk usage inside the container
df -H --output=source,size,used,avail
Filesystem Size Used Avail
overlay 26G 24G 605M
tmpfs 68M 0 68M
shm 68M 0 68M
/dev/sda3 26G 24G 605M
tmpfs 749M 13M 736M
tmpfs 3.8G 0 3.8G
tmpfs 3.8G 0 3.8G
tmpfs 3.8G 0 3.8G
tmpfs 3.8G 0 3.8G
The compressed image size is 332.79 M. Could this be a disk space issue?
Progress.
From the look of things it was a disk space issue. I freed up 700Mb of disk space and now I no longer get the HTTP 206 errors, but now the problem appears to be the repo url, as shown below:
Running with gitlab-runner 15.11.0 (436955cb)
on docker-runner Uz5x5rch, system ID: r_YBpnILRXCEuA
Preparing the "docker" executor
Using Docker executor with image ubuntu-22.04.myguest.virtualbox.org:80/gitlab-instance-af848a70/dependency_proxy/containers/python:3.10.11 ...
Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image ubuntu-22.04.myguest.virtualbox.org:80/gitlab-instance-af848a70/dependency_proxy/containers/python:3.10.11 ...
Using docker image sha256:fc98d03e603711443ee94a56ea857491d9d8e1dc6bc32721e7a4f995360e9e76 for ubuntu-22.04.myguest.virtualbox.org:80/gitlab-instance-af848a70/dependency_proxy/containers/python:3.10.11 with digest ubuntu-22.04.myguest.virtualbox.org:80/gitlab-instance-af848a70/dependency_proxy/containers/python@sha256:b48e216f7c4adcf24fecd7016f3b8ead76866a19571819f67f47c1ccaf899717 ...
Preparing environment
00:01
Running on runner-uz5x5rch-project-2-concurrent-0 via 25b4b4311eed...
Getting source from Git repository
00:00
Fetching changes with git depth set to 20...
Reinitialized existing Git repository in /builds/gitlab-instance-af848a70/testproject/.git/
fatal: unable to access 'http://ubuntu-22.04.myguest.virtualbox.org/gitlab-instance-af848a70/testproject.git/': Could not resolve host: ubuntu-22.04.myguest.virtualbox.org
ERROR: Job failed: exit code 1
What is odd though is that I registered my runner with a local IP address gitlab-runner register --url http://172.12.16.1/ --registration-token ABCDEFGHIJLKM-12345abcdefghijk but the runner keeps trying to pull the repo using the domain name in the instructions (below) for running a creating a runner
sudo gitlab-runner register --url http://ubuntu-22.04.myguest.virtualbox.org/ --registration-token $REGISTRATION_TOKEN
Update: problem appears to be that somehow the repo domain names are http://ubuntu-22.04.myguest.virtualbox.org/, not IP addresses, and there does not appear to be a way to change this.
I never managed to solve the repo domain name issue, but the HTTP 206 error disappeared and the image was successfully pulled after I freed up 700Mb of disk space
PS: myguest.virtualbox.org is the domain name assigned to my virtual box at install time.