Pushing to registry is timing out
See original GitHub issueDescription 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
Issue Analytics
- State:
- Created 5 years ago
- Comments:23 (18 by maintainers)
Top Results From Across the Web
Unable to push Docker images to local registry, client times out
I'm trying to push an image to a local registry I deployed on port 5000. When I use this command docker push localhost:5000/explorecalifornia....
Read more >Pushing image in private docker registry fails due to timeout
I downloaded a alpine image from docker hub, tagged it and tried to push it, but i got timeout error.
Read more >User getting timeout while pushing to registry.gitlab.com
A GitLab.com is getting the following error sporadically while pushing a new image from a CI runner. It seems an odd endpoint to...
Read more >1335279 – 504 gateway timeouts on 'docker push' to registry ...
Description of problem: After 4 tries, receive 504 gateway timeout errors on image pushes (see log below). Version-Release number of selected component (if ......
Read more >Push Docker image to Azure Container Registry timeout and ...
I'm getting two different problems that switch back and forth when trying to use VSTS Build to push an image to Azure Container...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@coollog Hey, thanks for your support. This helped me a lot and is running now!
@chanseokoh Ah right, we should just have it as
jib.httpTimeout
then, and set both connection timeout and read timeout as that.