Skip to content

Dependency Proxy is pulling the image with wrong architecture

Summary

I have a self-hosted GitLab instance hosted on newest AWS EC2 instance based on AWS Graviton2 ARM processor. Both GitLab and GitLab Runner are running on ARM64 architecture.

By default, docker pull will automatically pull the correct image for the runner architecture.

I have a CI that is using the node:14 image. I have configured Dependency Proxy for my CI, and it is pulling the linux/amd64 image instead of linux/arm64/v8.

Steps to reproduce

Example Project

N/A. This is on a self-hosted instance.

What is the current bug behavior?

GitLab Runner is pulling the image with wrong architecture. In this case, node:14 image of linux/amd64 platform.

What is the expected correct behavior?

It should pull the node:14 image of linux/arm/v8 platform.

Relevant logs and/or screenshots

Before configuring Dependency Proxy

image


After configuring Dependency Proxy

image

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info
# gitlab-rake gitlab:env:info

System information
System:		Ubuntu 20.04
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.7.2p137
Gem Version:	3.1.4
Bundler Version:2.1.4
Rake Version:	13.0.3
Redis Version:	6.0.10
Git Version:	2.29.0
Sidekiq Version:5.2.9
Go Version:	unknown

GitLab information
Version:	13.10.0-ee
Revision:	0d2d9558dba
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	PostgreSQL
DB Version:	12.5
URL:		https://gitlab.PRIVATE-INSTANCE.com
HTTP Clone URL:	https://gitlab.PRIVATE-INSTANCE.com/some-group/some-project.git
SSH Clone URL:	[email protected]:some-group/some-project.git
Elasticsearch:	no
Geo:		no
Using LDAP:	no
Using Omniauth:	no

GitLab Shell
Version:	13.17.0
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
GitLab Shell path:		/opt/gitlab/embedded/service/gitlab-shell
Git:		/opt/gitlab/embedded/bin/git

Expand for output related to GitLab instance system information
# uname -a
Linux ip-172-31-36-17 5.4.0-1039-aws #41-Ubuntu SMP Wed Feb 24 23:14:54 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
Expand for output related to GitLab Runner instance system information
# uname -a
Linux ip-172-31-36-1 5.4.0-1039-aws #41-Ubuntu SMP Wed Feb 24 23:14:54 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

Results of GitLab application Check

Expand for output related to the GitLab application check
# gitlab-rake gitlab:check SANITIZE=true

Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 13.17.0 ? ... OK (13.17.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes Number of Sidekiq processes (cluster/worker) ... 1/1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 2/1 ... yes 16/3 ... yes 14/4 ... yes 14/5 ... yes 14/6 ... yes 17/7 ... yes 15/8 ... yes 4/10 ... yes 20/11 ... yes 20/12 ... yes 15/13 ... yes 21/14 ... yes 21/15 ... yes 17/16 ... yes 15/17 ... yes 9/19 ... yes Redis version >= 4.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (2.7.2) Git version >= 2.29.0 ? ... yes (2.29.0) Git user has default SSH configuration? ... yes Active users: ... 13 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 7.x (6.4 - 6.x deprecated to be removed in 13.8)? ... skipped (elasticsearch is disabled)

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished

Possible fixes