-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
"COPY ." not copying all files to the image #1110
Comments
Hi @alexfrancavilla do you think it's possible to setup a very simple project that shows the issue? |
Hi @dgageot sure thing! I've setup a repository here: alexfrancavilla/skaffold-issue-1110, which looks equal to what I've explained above. Steps to reproduce:
PS: Assuming you're running macOS and want to use
Thanks for taking care! |
@alexfrancavilla OK. So I reproduced the issue. I'll try to understand what's going on |
It looks like it's because of the |
Fixes GoogleContainerTools#1110 Signed-off-by: David Gageot <[email protected]>
Amazing! I've just built your fix-1110 branch and can confirm that it works perfectly. Thank you very much for your quick help. Cheers! |
Hi there. I've recently updated my skaffold version which broke the image building process. Usually I work with Skaffold + Minikube + Helm. The following Dockerfile line behaves differently:
I've nailed it down to work with skaffold 0.10.0 and breaks with 0.11.0 (also the newest version 0.15.1 is affected for me). What happens is that the COPY task is not adding ALL files to the image but is missing some. The "some" is a little hard to describe, it is always the same files and not randomly, but is different between projects. In an extremely simple Nodejs/Express project the task only added the Dockerfile, and misses the
src/
dir as well as top level config files liketsconfig.json
. In another PHP project other (randomly looking) directories and files are affected.The building process then goes on and my project will eventually fail at runtime because of missing sources or other relevant stuff.
It may be worth noting that every project for me has the skaffold.yaml file in a different directory. The node project's skaffold file is located in a separate repository (
../dev/skaffold.yaml
), the PHP project stores it in a subdirectory (build/skaffold.yaml
).The Dockerfile has not changed, usual
docker build .
commands result in the same working image as the 0.10.0 skaffold version.My workaround is to use
COPY * dest/
instead ofCOPY . dest/
, but this obviously may skip hidden files/directories.Information
skaffold.yaml (0.11.0+)
skaffold.yaml (0.10.0)
Dockerfile
.dockerignore of the project (if that is relevant)
The text was updated successfully, but these errors were encountered: