-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MojoExecutionException: Invalid image creation time: 2020-04-21T13:22:10.836777828-07:00 #2428
Comments
Hi @YanzheL, I don't know what base image you are using, but the offending timestamp ( And looks like
We will investigate this further. |
Interesting, so this is a JDK issue. Can’t believe this bug shows in JDK LTS version. Is this timestamp special? BTW, the base image is |
@YanzheL I can't say yet this is a JDK issue. ATM, it just seems like UPDATE: see https://stackoverflow.com/a/61465927/1701388. Java 12 and higher can parse a string with an offset. |
@YanzheL I checked the container config of
And how did you create the base image of date 04-21? Using |
JDK-8166138 is the corresponding bug and says that the fix is available starting from Java 12. Actual fix: http://hg.openjdk.java.net/jdk/jdk/rev/6f58ecdb060a Maybe we can try one of the solutions in https://stackoverflow.com/q/51284995/1701388 when |
@chanseokoh
|
Maybe this is because Docker Buildkit produces timestamps in different format which contain an offset that JDK 11 cannot parse?
If I build the base image with docker buildkit disabled, the timestamp
|
@YanzheL Jib 2.3.0 is released with this fix! |
Environment:
maven:3-jdk-11
maven:3-jdk-11
Description of the issue:
The JIB build passes with builder image
maven:3-jdk-14
in GitLab-CI, but fails onmaven:3-jdk-11
. The error message is weird and I cannot reproduce it if JDK > 11.In my local environment the build passes.
Expected behavior:
Build on
maven:3-jdk-11
.Steps to reproduce:
jib-maven-plugin
Configuration:Log output:
Additional Information:
The text was updated successfully, but these errors were encountered: