-
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 build directory copy fails #1110
Comments
Thanks @tarvitz . I have this PR #1114 and #1113 which ended up fixing this
Here i used the
|
Can you use the latest image?
|
Checked with executor:edge, here's result:
Dockerfile is the same. |
@tejal29 I just tried the latest version you posted above (not including the warmer) and I am still getting a similar error
I was able to resolve the issue by using gcr.io/kaniko-project/executor:debug-v0.17.1 |
Hello, I'm adding some noise to this thread to find this issue via Google if somebody else have an issue in their CI/CD. So, sorry if my comment is not relevant for the issue resolution. This issue cause a failure in many of our gitlab CD, we've switched to debug-v0.17.1 too, solving the issue. I guess that gitlab documentation should not recommand to configure on As a reference, our DockerFile, and our .gitlab-ci.yml in version 1.4.5 are affected by this issue, and this project is opensource. Here, we are doing an Best regards, |
For me v0.19.0 has fixed the issue. |
I've updated back to gcr.io/kaniko-project/executor:debug works fine with copying virtual environment directory of python (like in the example above). |
I just tested with
It's failing.
|
Is it resolved? I am still facing this issue. |
Yes, the latest version of Kaniko works fine against the problem I've reported (I've just taken a look if builds are being built and they're fine). |
Actual behavior
Multistage build fails.
The latest kaniko result build and output:
Output:
Expected behavior
Multistage build runs well.
Output with kaniko: gcr.io/kaniko-project/executor:v0.17.1
To Reproduce
Steps to reproduce the behavior:
Additional Information
Dockerfile:
Build context not required
Kaniko images:
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: