jib:build Remaining allocation units less than 0

Description of the issue: The jib-maven-plugin failed with this error message: org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.google.cloud.tools:jib-maven-plugin:1.0.1:build (default-cli) on project backend: Remaining allocation units less than 0 for 'pull container configuration sha256:0ea51d9f12788eb9ab2fad601aeda6fd2d444fde75b1cfb853994913ed88243d': -1

I use Nexus 3 as a local Docker repository for my images, and as a proxy to Docker Hub. In front of Nexus, I have a Traefik, which setup itself from Docker labels.

The docker labels of the Nexus repository:

• traefik.docker.network=public
• traefik.frontend.entryPoints=http,https
• traefik.app.port=8081
• traefik.app.frontend.rule=Host:nexus.192.168.100.101.nip.io
• traefik.registry_pull.port=5055
• traefik.registry_pull.frontend.rule=Host:nexus.192.168.100.101.nip.io;PathPrefix:/v2;Method: GET
• traefik.registry_pull.priority=30
• traefik.registry_push_1.port=5050
• traefik.registry_push_1.frontend.rule=Host:nexus.192.168.100.101.nip.io; PathPrefix:/v2
• traefik.registry_push_1.priority=20
• traefik.registry_push_2.port=5050
• traefik.registry_push_2.frontend.rule=Host:nexus.192.168.100.101.nip.io; PathPrefix:^/(v1|v2)/[^/]+/?[^/]+/blobs/;Method: POST, PUT, PATCH, DELETE, HEAD
• traefik.registry_push_2.priority=40

With this configuration, the docker pull nexus.192.168.100.101.nip.io/alpine:latest and others work as expected, but jib cannot pull docker layers. If a publish the port 5050, 5055, and configure jib to pull and push from/to these ports, then jib works as expected.

Environment: Build from Jenkins Pipeline with Docker Maven container (maven:3-jdk-11-slim)

jib-maven-plugin Configuration (relevant section):

<plugin>
	<groupId>com.google.cloud.tools</groupId>
	<artifactId>jib-maven-plugin</artifactId>
	<version>1.0.1</version>
	<configuration>
		<allowInsecureRegistries>true</allowInsecureRegistries>
		<from>
			<!--suppress UnresolvedMavenProperty -->
			<image>${nexus.location}/adoptopenjdk/openjdk11:alpine</image>
		</from>
		<to>
			<!--suppress UnresolvedMavenProperty -->
			<image>${nexus.location}/mekh/phonebook-backend:${project.version}</image>
		</to>
		<container>
			<ports>
				<port>8080</port>
			</ports>
		</container>
	</configuration>
</plugin>

Additional Information: The jib-maven-plugin:1.0.0 can use HTTP, but the jib-maven-plugin:1.0.1 works with only HTTPS connection.

[chanseokoh]

@mecseid v1.0.2 released that will prevent crashing when enabling compression. v1.0.2 also fixes the regression that may fail to try HTTP.

[chanseokoh]

I think we know why compression is causing this issue. This shouldn’t be specific to Traefik. The root cause of the inaccurate/incomplete progress usage is probably #1522.

Anyways, #1521 will make Jib proceed normally with inaccurate/incomplete progress usage, so I expect #1521 will unblock you.