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
When using the COPY command, if the source and destination have the same
the file should be skipped rather than copied. This is to prevent the
file from being overwritten and therefore producing an empty file.
fixesGoogleContainerTools#904
poy
added a commit
to poy/kaniko
that referenced
this issue
Dec 8, 2019
When using the COPY command, if the source and destination have the same
the file should be skipped rather than copied. This is to prevent the
file from being overwritten and therefore producing an empty file.
fixesGoogleContainerTools#904
When using the COPY command, if the source and destination have the same
the file should be skipped rather than copied. This is to prevent the
file from being overwritten and therefore producing an empty file.
fixesGoogleContainerTools#904
Actual behavior
COPY results in the expected directory structure and files, but the files are empty.
Expected behavior
When using the
COPY
command on a directory structure that has some depth, I would expect the files and their contents to be copied.To Reproduce
Steps to reproduce the behavior:
cloudbuild.yaml
:gcloud builds submit . --config=cloudbuild.yaml
Additional Information
Please provide either the Dockerfile you're trying to build or one that can reproduce this error.
Please provide or clearly describe any files needed to build the Dockerfile (ADD/COPY commands)
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: