You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a multistage Dockerfile which has COPY commands in multiple stages copying contents of directories. In one instance the directory contains files as a direct children. In another, it's a mix with files and many directories which also have files and directories.
When files changed in the first directory Kaniko notices it and runs COPY command, but when files change in the seconds, couple levels down from the directory root, Kaniko uses cached layer.
The questions I have are:
Do I use it correctly or not ?
Are my expectations reasonable and this is a bug ?
The text was updated successfully, but these errors were encountered:
I have a multistage Dockerfile which has
COPY
commands in multiple stages copying contents of directories. In one instance the directory contains files as a direct children. In another, it's a mix with files and many directories which also have files and directories.When files changed in the first directory Kaniko notices it and runs COPY command, but when files change in the seconds, couple levels down from the directory root, Kaniko uses cached layer.
The questions I have are:
The text was updated successfully, but these errors were encountered: