-
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
Missing files in node_modules when using --use-new-run=true #1316
Comments
Thanks @fabiotamagno for the feedback. |
Confirming that I also see this issue! Would really like to see this fixed as the new run command was SO much faster, however all my projects are node... |
@msembinelli i did not get time to investigate this. Did you try using the new |
hey @fabiotamagno, i had a small bug in the code #1379
I verified this image here #1317 (comment) |
closing as dupe of #1317 |
@tejal29 didn't work for me, maybe the issue is different? I also have a build that includes node_modules and it's missing when I build using kaniko (with the image you provided). |
I am also seeing this and baffled. Our |
Actual behavior
With
--use-new-run=true
, files that exist on the first kaniko run under./node_modules/
folder, are not available when using the cache.This happens with the same pattern on every run, and the same files are missing.
The following is from a run with caches:
(above there should be at least index.js)
(above there should be dozens of symlinks)
On first build, without caches available, the following appears a couple times:
Expected behavior
The same files should be present on every run, even from cache.
To Reproduce
Steps to reproduce the behavior:
Additional Information
gcr.io/kaniko-project/executor@sha256:9f17434aa98dc64d98350dee516927bebae1a1d40a9cac305d1d5e5864e4c850
debug-perf
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: