Unable to execute manylinux1 pypa image
Summary
When trying to use manylinux1 image: quay.io/pypa/manylinux1_x86_64 (see https://github.com/pypa/manylinux) the runner is unable to run the image and fails with a panic message.
Steps to reproduce
Define a gitlab CI job in a dummy project which uses quay.io/pypa/manylinux1_x86_64 run the job either locally with gitlab-runner command line or in a proper CI setup. And you'll get:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xd1428b]
.gitlab-ci.yml
many1_usage:
stage: whatever
image: quay.io/pypa/manylinux1_x86_64
script:
- ls -la
Actual behavior
In our on-premise CI (Gitlab CE - 12.5.5), I get:
ERROR: Job failed: exit code 139
Expected behavior
Seeing ls result and a successful job.
Relevant logs and/or screenshots
Environment description
On premise Gitlab CE 12.5.5 and/or local gitlab-runner 12.7.1.
Used GitLab Runner version
In our CI we have:
Running with gitlab-runner 12.5.0 (577f813d)
on XXXXXX
Using Docker executor with image quay.io/pypa/manylinux1_x86_64 ...
Pulling docker image quay.io/pypa/manylinux1_x86_64 ...
Using docker image sha256:e93feb267715eeaf4faafeb3647f0a8f2474338a394cf6739f0ea7d0fbde98ba for quay.io/pypa/manylinux1_x86_64 ...
I tried a local execution too:
$gitlab-runner exec docker many1_usage
Runtime platform arch=amd64 os=linux pid=5634 revision=003fe500 version=12.7.1
Running with gitlab-runner 12.7.1 (003fe500)
Using Docker executor with image quay.io/pypa/manylinux1_x86_64 ...
Pulling docker image quay.io/pypa/manylinux1_x86_64 ...
Using docker image sha256:e93feb267715eeaf4faafeb3647f0a8f2474338a394cf6739f0ea7d0fbde98ba for quay.io/pypa/manylinux1_x86_64 ...
Authenticating with credentials from /home/XXX/.docker/config.json
Running on runner--project-0-concurrent-0 via localhost...
Authenticating with credentials from /home/XXX/.docker/config.json
Fetching changes...
Initialized empty Git repository in /builds/project-0/.git/
Created fresh repository.
From /home/XXX/manylinux-bug
* [new branch] master -> origin/master
Checking out af3f5c0b as master...
Skipping Git submodules setup
Authenticating with credentials from /home/XXX/.docker/config.json
Authenticating with credentials from /home/XXX/.docker/config.json
Authenticating with credentials from /home/XXX/.docker/config.json
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xd1428b]
goroutine 50 [running]:
gitlab.com/gitlab-org/gitlab-runner/common.(*Build).executeUploadReferees(0xc000119880, 0x19f3ae0, 0xc00026a340, 0xbf8ab18c5d204055, 0x885798fd, 0x251d920, 0xbf8ab18f1b55cab0, 0x31633d171, 0x251d920)
/builds/gitlab-org/gitlab-runner/common/build.go:336 +0x35b
gitlab.com/gitlab-org/gitlab-runner/common.(*Build).executeScript(0xc000119880, 0x19f3ae0, 0xc00026a340, 0x1a06a20, 0xc000316800, 0x0, 0x0)
/builds/gitlab-org/gitlab-runner/common/build.go:297 +0x1fc
gitlab.com/gitlab-org/gitlab-runner/common.(*Build).run.func1(0xc0005b2300, 0xc000119880, 0x19f3ae0, 0xc00026a340, 0x1a06a20, 0xc000316800)
/builds/gitlab-org/gitlab-runner/common/build.go:401 +0x56
created by gitlab.com/gitlab-org/gitlab-runner/common.(*Build).run
/builds/gitlab-org/gitlab-runner/common/build.go:400 +0x214
Possible fixes
N/A
Edited by Eric NOULARD