Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Timeout on Artifactory when pushing a small container config JSON
See original GitHub issueEnvironment:
- Jib version: 2.8.0,2.7.1
- Build tool: maven
- OS: CentOS
Description of the issue: Image with layers which contain ~200MB cannot be pushed.
Expected behavior:
It should be pushed because push over docker push works as expected.
Steps to reproduce:
- make image with fat layers at least one layer should be 200mb
- perform pushing ver jib
jib-maven-plugin Configuration:
default one
Log output:
[DEBUG] TIMING pushBlob
[DEBUG] TIMING pushBlob POST sha256:8446047073737851b91f598b5d551e2d5a1e0de81e7fa3687d0d020714eacfeb
[DEBUG] TIMED pushBlob PATCH sha256:8446047073737851b91f598b5d551e2d5a1e0de81e7fa3687d0d020714eacfeb : 36.058 ms
[ERROR] [31;1mI/O error for image [docker/service]:[0m
[ERROR] [31;1m java.net.SocketTimeoutException[0m
[ERROR] [31;1m Read timed out[0m
[DEBUG] TIMED pushBlob POST sha256:8446047073737851b91f598b5d551e2d5a1e0de81e7fa3687d0d020714eacfeb : 120131.764 ms
[DEBUG] TIMED pushBlob : 120168.162 ms
[DEBUG] TIMED Pushing BLOB digest: sha256:8446047073737851b91f598b5d551e2d5a1e0de81e7fa3687d0d020714eacfeb, size: 11396 : 120207.379 ms
[DEBUG] TIMED Pushing container configuration : 120231.589 ms
[DEBUG] TIMED Building and pushing image : 124849.373 ms
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
How do I resolve build info deployment timeouts? - JFrog
When the Jenkins Artifactory Plugin deploys build-info, it opens a connection to Artifactory, which triggers it to execute several processes ...
Read more >Knowledge Base - JFrog
This video goes over how to install JFrog Xray 3.x with a HA configuration in a GKE environment. Prerequisites: Basic knowledge of how...
Read more >How to set Artifactory UI session timeout? - JFrog
$ARTIFACTORY_HOME/etc/artifactory.system.properties file. By adding the timeout property, as artifactory.ui.session.timeout.minutes=X, ...
Read more >Helm Charts for Advanced Users - JFrog - JFrog Documentation
In this chart, you will set the type of storage you want using artifactory.persistence.type and pass the required configuration settings. The ...
Read more >google jib-maven-plugin socket read timeout error ... - JFrog
We are using Artifactory Commercial license 7.15.4 rev 71504900 as our docker repo and noticed sometimes when pushing docker images with ...
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 Free
Top 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
@chanseokoh yes, the issue happens regardless of this setting.
@chanseokoh i managed to reproduce this and get logs - looks like read timeout occurs when pushing payload of only 11566 bytes. using maven 3.8.1, adopt-openjdk16, jib 3.1.2
Strangely, when I test on some other project where I added layer >250MB in size timeout does not happen. But on this project I can consistently reproduce this behavior - it happens even if I use 120 seconds http timeout using option
-Djib.httpTimeout=120000. It also happens on different machines (could repro it on my machine but also on a jenkins build machine).maven-jib-312-read-timeout-log.txt