jib: Pushing to registry is timing out

Description of the issue: Our docker-registry is sometimes a little bit slow, so the building-process inside our CI-pipeline fails with the message Build image failed: Read timed out. The timeout i selected inside my settings.xml for this server is not respected.

Expected behavior: Respecting the Timeout inside the servers-tag in settings.xml

Steps to reproduce: Try to push an image to an slow docker-registry. Then set the timeout for this registry inside your settings.xml and test ist again. You will see that the timeout is not respected.

Tested with version 0.9.6

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 23 (18 by maintainers)

Most upvoted comments

Hi, @alexanderzimmer we’ve just release version 0.9.7 - can you try with that version and using the jib.httpTimeout system property?

For example:

mvn compile jib:build -Djib.httpTimeout=60000

coollog on Jul 20, 2018

@coollog Hey, thanks for your support. This helped me a lot and is running now!

alexzimmer96 on Jul 26, 2018

@chanseokoh Ah right, we should just have it as jib.httpTimeout then, and set both connection timeout and read timeout as that.

coollog on Jul 13, 2018