-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Jib should read the Docker environment variables and daemon.json #1551
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Since dockerhub introduced the pull limits, this closed issue is now relevant. |
@PavelGloba Mind to explain to us why you'd like to have Jib follow the same workflow that the Docker daemon goes through regarding |
@chanseokoh Well, the reason is the same as why registry-mirrors exists in daemon.json |
Reopened #1396 about the |
@PavelGloba to better support the users hitting the Docker Hub rate limiting, we implemented the registry mirror feature, which is now live with the Jib 2.8.0 release. Check out this FAQ to learn how to configure it. |
Closing issue as |
Jib should seed itself with Docker configuration when available.
Environment
The docker-provided
inspectDockerImage
tool supports the following environment variables:DOCKER_REGISTRY_AUTH_ENDPOINT
, defaults tohttps://registry-1.docker.io
DOCKER_REGISTRY_API_ENDPOINT
, defaults tohttps://auth.docker.io
daemon.json
The Docker
daemon.json
file configures:insecure-registries
a set of registries allowed to be HTTP-onlyregistry-mirrors
: a set of mirrors to consult, sometimes used to reference country-level mirrors like Docker's China Mirror.The daemon.json file lives at:
/etc/docker/daemon.json
on Linux%ProgramData%\docker\config\daemon.json
on Windows~/.docker/daemon.json
on macOS (not documented, but it's there)The text was updated successfully, but these errors were encountered: