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.
Jib-gradle-plugin jib.httpTimeout not taken into account
See original GitHub issueEnvironment:
- Jib version: 2.6.0
- Build tool: gradle 6.7
Description of the issue:
Getting the following error when building:
15:27:50 Container entrypoint set to [java, -XX:MaxMetaspaceSize=512m, -Djava.security.egd=file:/dev/./urandom, -javaagent:/app/WEB-INF/lib/otel-javaagent.jar, -Dotel.instrumentation.jdbc-datasource.enabled=false, -Dotel.instrumentation.servlet-filter.enabled=true, -Dotel.instrumentation.servlet-service.enabled=true, -cp, /app/resources:/app/classes:/app/libs/*, ...] 15:28:22 [31;1mI/O error for image [docker-staging.repository.collibra.io/arch/dgc-aggregator]:[0m 15:28:22 [31;1m java.net.SocketTimeoutException[0m 15:28:22 [31;1m Read timed out[0m
gradle.properties contain the following property
jib.httpTimeout=0
Never the less from the logs you can see it times out after ±20 seconds.
It seems the property doesn’t have any effect.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Oh, I see the confusion. They are system properties.
Yeah correct, just a bit odd to use jvm properties. The Gradle way would be to use project properties instead that’s why am confused 😃