-
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
Subsequent Builds fail when using cache #742
Comments
@BenHizak Thank you for the detail report along with the files to reproduce this. Thanks |
I have been able to reproduce this issue on my GCP project using a local build. I'm finding interesting behavior. If I clean the cache between runs I get different errors: OR DEBU[0005] creating file /usr/bin/reindexdb OR DEBU[0005] creating file /usr/bin/reindexdb |
If I pull the cache and look in the image's overlay2 I see all mentioned files/directories: |
After investigating this, it turns out the issue is NOT with caching. The problem is in how we interpret Dockerfile. The command in the example Dockerfile: Changing the Dockerfile to: Doing a docker build of the Dockerfile with: |
Actual behavior
When building with
--cache
, the first build succeeds, but subsequent builds fail.Expected behavior
If a build succeeded once, I expect the build to work every single time (as long as the code didn't change)
To Reproduce
Dockerfile, build context, logs, and other materials can be found here
Additional Information
The Error is always as follows. (the folder is different)
Kaniko Image
This problem was replicated with both images
The text was updated successfully, but these errors were encountered: