-
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
Multistage builds doesn't always bust the cache correctly #845
Labels
area/caching
For all bugs related to cache issues
area/multi-stage builds
issues related to kaniko multi-stage builds
Comments
noticed that this probably is a duplicate of #589 |
priyawadhwa
added
area/multi-stage builds
issues related to kaniko multi-stage builds
area/caching
For all bugs related to cache issues
labels
Nov 8, 2019
1 task
I've tested with the latest master (a675098) and this seems to have been solved |
Thanks for verifying @fredr . Closing this issue but feel free to reopen if needed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/caching
For all bugs related to cache issues
area/multi-stage builds
issues related to kaniko multi-stage builds
Actual behavior
When copying files from an other stage and then chowning the files, the chown command will be cached even though the files being copied have change, causing the cache to overwrite all changes.
Expected behavior
I would expect the cache to be busted after the
COPY
-command if the files have changed.To Reproduce
Steps to reproduce the behavior:
myfile
to anything else and rerun step 1.It will still return
VALUE
Additional Information
The Dockerfile:
The file beeing copied:
myfile
(content doesn't matter)Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: