Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Jib should read the Docker environment variables and daemon.json

See original GitHub issue

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 to https://registry-1.docker.io
DOCKER_REGISTRY_API_ENDPOINT, defaults to https://auth.docker.io

`daemon.json`

The Docker daemon.json file configures:

insecure-registries a set of registries allowed to be HTTP-only
registry-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)

Issue Analytics

State:
Created 5 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

chanseokohcommented, Feb 24, 2021

@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.

0reactions

mpeddada1commented, Aug 5, 2022

Closing issue as registry-mirror support is now available in the plugins and Jib CLI through a global config file (see README). Please re-open if this feature is still relevant.