Pipeline fails when using some docker images with `error standard_init_linux.go:190: exec user process caused "no such file or directory"`
Summary
Some Docker images, especially for ARM64 architecture, are failing to deploy due to the following error:
standard_init_linux.go:190: exec user process caused "no such file or directory"
Steps to reproduce
Sample .gitlab-ci.yml
stages:
- build
build-it:
stage: build
image: "arm64v8/ubuntu:rolling"
script:
- echo "hello world"
stages:
- build
build-it:
stage: build
image: "ubuntu@sha256:0822361370fbe0b609cbc7a15097679adcd51f7094d99c8bd37944d98e19521b"
script:
- echo "hello world"
Example Project
https://gitlab.com/ealap/how-to-ci/-/pipelines
What is the current bug behavior?
Pipeline is failing
What is the expected correct behavior?
Pipeline should build just fine
Relevant logs and/or screenshots
Full console log
Running with gitlab-runner 13.9.0-rc2 (69c049fd) on docker-auto-scale 72989761 feature flags: FF_GITLAB_REGISTRY_HELPER_IMAGE:true Preparing the "docker+machine" executor 00:08 Using Docker executor with image arm64v8/ubuntu:rolling ... Pulling docker image arm64v8/ubuntu:rolling ... Using docker image sha256:d9d2dbb271fc8e0c33e569ce43dc0c9bdbe61d254c3fd38a50df83d63862c0a4 for arm64v8/ubuntu:rolling with digest arm64v8/ubuntu@sha256:0822361370fbe0b609cbc7a15097679adcd51f7094d99c8bd37944d98e19521b ... Preparing environment 00:01 Running on runner-72989761-project-25782303-concurrent-0 via runner-72989761-srm-1618123357-7331f27c... Getting source from Git repository 00:01 $ eval "$CI_PRE_CLONE_SCRIPT" Fetching changes with git depth set to 50... Initialized empty Git repository in /builds/ealap/learn-ci/.git/ Created fresh repository. Checking out a86da529 as master... Skipping Git submodules setup Executing "step_script" stage of the job script 00:01 Using docker image sha256:d9d2dbb271fc8e0c33e569ce43dc0c9bdbe61d254c3fd38a50df83d63862c0a4 for arm64v8/ubuntu:rolling with digest arm64v8/ubuntu@sha256:0822361370fbe0b609cbc7a15097679adcd51f7094d99c8bd37944d98e19521b ... standard_init_linux.go:190: exec user process caused "no such file or directory" Running after_script 00:01 standard_init_linux.go:190: exec user process caused "no such file or directory" Cleaning up file based variables 00:00 ERROR: Job failed: exit code 1
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)