Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow custom registry/proxy #1453

Open
akhayyat opened this issue Dec 9, 2024 · 1 comment
Open

Allow custom registry/proxy #1453

akhayyat opened this issue Dec 9, 2024 · 1 comment

Comments

@akhayyat
Copy link

akhayyat commented Dec 9, 2024

Problem: In an environment where direct Internet access is not available and a local docker registry proxy is used, all docker hub images are available as docker.my.tld/<docker-hub-name>.
Consequently, the image docker.io/firecow/gitlab-ci-local-util:latest cannot be pulled.

Suggested solution: Provide means to configure the docker registry URL (replacement for docker.io), e.g. a DOCKER_REGISTRY configuration variable.

In the meantime, one possible alternative is to configure the Docker daemon to use a registry mirror as documented here:
https://docs.docker.com/docker-hub/mirror/#configure-the-docker-daemon

@ANGkeith
Copy link
Collaborator

ANGkeith commented Dec 13, 2024

In the meantime, one possible alternative is to configure the Docker daemon to use a registry mirror as documented here:
https://docs.docker.com/docker-hub/mirror/#configure-the-docker-daemon

In my opinion, your proposed alternative is sufficient.

I don’t see the need to implement this in gitlab-ci-local, since docker is unlikely to function properly without configuring the docker daemon. You would eventually need to update the configuration there as well, so might as well handle it directly at that level, effectively solving two problems with a single configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants