Maven Downloads Work, but Jib Cannot Pull the Base Image

Locate the failed repository or registry request, then apply the proxy configuration used by the component making it.

The Maven dependencies download, then Jib fails while contacting a registry. That is a useful clue: Maven repository access worked, but it did not exercise Jib's registry client.

Start with the failed URL

Failed operationProxy configuration to inspect
Maven plug-in or dependency retrievalThe active settings.xml repository proxy and exclusions.
Jib base-image or registry token requestThe Java networking properties Jib uses for registry communication.

For an unauthenticated HTTP intermediary, supply the Jib route in the Maven invocation:

mvn -Dhttp.proxyHost=proxy.example.net \
    -Dhttp.proxyPort=8080 \
    -Dhttps.proxyHost=proxy.example.net \
    -Dhttps.proxyPort=8080 \
    -Dhttp.nonProxyHosts='localhost|127.*|*.internal.example' \
    jib:buildTar

Use the actual proxy host and port while retaining the project's Jib image settings. For a public registry and token service on a permitted public-proxy route, the HTTP proxy list supplies candidates for these unauthenticated proxy fields. The host properties take hostnames, without an http:// prefix. The https properties select the proxy for HTTPS destinations; Java uses http.nonProxyHosts for the HTTPS bypass list too.

A local archive can still require a pull

jib:buildTar writes its resulting image archive locally. It can nevertheless need network access to obtain the base image first. Choosing that output does not remove the registry request.

After changing configuration, compare the failed URL again. Keep working Maven repository settings in place, and diagnose any remaining registry or token-service failure on Jib's path.

Allakkat attuumassuteqartut