-
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
skaffold build fails if a Dockerfile
includes a COPY with a wildcard
#709
Comments
BTW this didn't use to be an issue for 0.4.x to 0.5.x of Skaffold so I guess something's changed in the handling of source |
@jstrachan i cant reproduce on skaffold 0.7.0
skaffold-vanilla build
Addendum. Can reproduce with your sample project. |
@dcherniv I just reproduced on skaffold 0.7.0:
I just checked its nothing to do with the
|
could it be dependent on the docker daemon version I wonder? I'm running the above inside a pod in GKE using kubernetes |
@jstrachan is your gke pod running linux running on windows? cause it might be this issue #693 |
its running linux - this is vanilla GKE stuff |
Should be fixed in 0.8.0 with #712 |
Expected behavior
Skaffold should build dockerfiles which use wildcards like this one (we kinda need wildcards for java)
Actual behavior
skaffold fails when it reaches the
COPY
with a wildcard:If I edit the
Dockerfile
to replace the*.jar
with a concrete file name then it all worksInformation
master
GKE pod running linux
Steps to reproduce the behavior
I'm using Jenkins X to test the above out but you should be able to reproduce on the CLI on a linux box.
Here's a sample project you can use to reproduce: https://github.com/jstrachan/demo97
then set the
VERSION & DOCKER_REGISTRY
env vars to something. e.g.The text was updated successfully, but these errors were encountered: