-
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
USER command fails when cache enabled #596
Comments
The workaround you suggested does not work, as the RUN layer come from the cache:
|
Yes, you are right, i guess it worked once as i was experimenting, |
@dlorenc It still does not work with the latest docker image I tried |
Unless #508 isnt actually deployed to the latest image, it doesnt fix the issue, but it was merged 2 months ago, so seems unlikely not to be live. |
Hey, You're right. I fixed the issue here in #600. I'll get a release out in a day or two, but you can test it from HEAD by building your own image or using: |
I dont like to be this person, but is that new release coming? |
It is working for us with gcr.io/kaniko-project/executor:debug-9912ccbf8d22bbafbf971124600fbb0b13b9cbd6 |
Actual behavior
USER cmd is failing with error,
open /etc/passwd: no such file or directory
, looks like the layer isnt getting unpacked to run this commandExpected behavior
Works
To Reproduce
Dockerfile:
Try and build it:
docker run -v $(pwd):/workspace gcr.io/kaniko-project/executor:latest --dockerfile Dockerfile --destination eu.gcr.io/ekreative-internal/kaniko-test --context dir://workspace --cache=true
Work around
Any other task before user causes layer to be unpacked, e.g.
RUN echo 1
Related to #508 (comment)
Versions tested:
gcr.io/kaniko-project/executor debug 58ba0d4767a9 6 days ago 46.8MB
gcr.io/kaniko-project/executor latest 025ab64f8cc8 3 weeks ago 45.8MB
The text was updated successfully, but these errors were encountered: