Dependency Proxy: Error response from daemon: received unexpected HTTP status: 599 status code 599
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Pipeline Jobs fail with HTTP 599 error from Dependency Proxy.
Steps to reproduce
- Trigger a Pipeline with Jobs which use Dependency Proxy.
What is the current bug behavior?
When a Pipeline Job runs, the following error is encountered:
Pulling docker image gitlab.REDACTED.com:443/REDACTED/dependency_proxy/containers/postgres:17.5 ...
WARNING: Failed to pull image with policy "always": Error response from daemon: received unexpected HTTP status: 599 status code 599 (manager.go:254:20s)
ERROR: Job failed: failed to pull image "gitlab.REDACTED.com:443/REDACTED/dependency_proxy/containers/postgres:17.5" with specified policies [always]: Error response from daemon: received unexpected HTTP status: 599 status code 599 (manager.go:254:20s)What is the expected correct behavior?
The Pipeline Job should run.
Relevant logs and/or screenshots
As above.
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 20.04 Current User: git Using RVM: no Ruby Version: 3.2.5 Gem Version: 3.6.5 Bundler Version:2.6.5 Rake Version: 13.0.6 Redis Version: 7.0.15 Sidekiq Version:7.2.4 Go Version: unknown GitLab information Version: 17.10.0 Revision: d8c1ba94b65 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 14.17 URL: https://gitlab.REDACTED.com HTTP Clone URL: https://gitlab.REDACTED.com/some-group/some-project.git SSH Clone URL: git@gitlab.REDACTED.com:some-group/some-project.git Using LDAP: no Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 14.41.0 Repository storages: - default: unix:/var/opt/gitlab/gitaly/gitaly.socket GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Gitaly - default Address: unix:/var/opt/gitlab/gitaly/gitaly.socket - default Version: 17.10.0 - default Git Version: 2.48.1.gl1
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab subtasks ...Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 14.41.0 ? ... OK (14.41.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/gitlab-shell-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 ...
Database config exists? ... yes Tables are truncated? ... skipped All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Cable config exists? ... yes Resque config exists? ... 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 Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units) Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units) Projects have namespace: ... REDACTED 600 lines, all "yes" Redis version >= 6.2.14? ... yes Ruby version >= 3.0.6 ? ... yes (3.2.5) Git user has default SSH configuration? ... yes Active users: ... 73 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished