Support registry-mirrors

[lxg1208]

Because of the network problems in some countries, the basic image cannot be pulled when build image with Jib. Whether the Jib can support a configuration like "registry-mirrors"?

[loosebazooka]

Can you explain your usecase.

You can always explicitly set the base image to something that is accessible in your country?

[lxg1208]

I can't pull images from Docker Hub with Jib most of the time.

[coollog]

Hi @lxg1208 , you can use jib.from.image to specify your own custom image from your desired registry mirror.

[chanseokoh]

you can use jib.from.image to specify your own custom image from your desired registry mirror.

You can't set jib.from.image to a pull-through mirror. For example, the mirror.gcr.io mirror (the public Google mirror on gcr.io for Docker Hub) doc says

Pulling cached images does not count against Docker Hub rate limits. However, there is no guarantee that a particular image will remain cached for an extended period of time. Only obtain cached images on mirror.gcr.io by configuring the Docker daemon. A request to pull directly from mirror.gcr.io will fail if a cached copy of the image does not exist.

This type of mirrors must be supported internally by Jib, as how --registry-mirror of Docker works.

[chanseokoh]

For future reference regarding mirror auth:

• https://stackoverflow.com/a/42758287/1701388
• Docker is not passing auth informations when pulling from a mirror registry moby/moby#30880

[chanseokoh]

For Jib Maven/Gradle plugins and Jib Core, this is fixed by #3011 and #2999. (Only public mirrors such as mirror.gcr.io are supported.) The mirror support will be useful when hitting Docker Hub rate limits.

I'll create a separate issue for Jib CLI.

[chanseokoh]

@lxg1208 Jib build plugins 2.8.0 is live with the feature to configure registry mirrors. It should be useful to avoid hitting the Docker Hub rate limiting. Check out this FAQ to learn how to configure it.