-
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
jib:build is not reproducible due to directory timestamps not being set #1648
Comments
Can you run docker history on the image to see if the digests are actually different? |
Seems like a critical bug. Timestamps of directories are not set to the epoch+1 sec.
We need to track down since when this started to happen. |
It doesn't have to run inside the container to reproduce. |
I think #1571 added this regression: https://github.com/GoogleContainerTools/jib/pull/1571/files#diff-9f3ce3d4c2254dbe95c91624e7b434d9R110 |
Moving the time code in the link above doesn't account for parent directories added with |
Gosh. That explains it. That is in 1.1.0. |
okay, fix is coming, behavior:
|
@eisig thanks again for reporting this. We just released 1.1.2 with the fix. |
Great 👍 |
Description of the issue:
When I build the code in container, it will rebuild all the layer every time.
Expected behavior:
I don’t have to wait for Docker to rebuild your entire Java application - just deploy the layers that changed.
Steps to reproduce:
examples/spring-boot
docker pull
the new image. I have to pull all the 3 layers, include the 14.38MB dependency layer every time .Environment:
macos 10.14.3, docker Version 2.0.0.3
The text was updated successfully, but these errors were encountered: