-
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
Building with --use-new-run=true
generates an incomplete image
#1317
Comments
Thanks @oohnoitz. this is high on my priority list and will take a look this Friday |
@oohnoitz Thanks for the project!
@oohnoitz I had a very simple bug in the code. I tried the image with fix #1379 you can now see non-empty layers. Can you please give this a try
|
@tejal29 I think there might be another issue with it when using multi-stage builds, which is resulting in some missing files on the final image. The sizes for the (pasting the output again for reference)
Due to the mismatch, the image still is missing some dependencies that should have been installed during the |
Thanks! Sorry for missing the size discrepancy earlier.
In this naive approach, we compute it before and after every run. This could be repetitive work if there are many run commands. |
I have published updated images
And the resulting image with this executor is:
|
Actual behavior
The
RUN
layers appear to be empty. I've done a few different scenarios and it seems to affect allRUN
layers after the firstRUN
command.I did a test without multistage build and here are the results: https://gist.github.com/oohnoitz/6d46b79619767f0c89bdee89be49689b which has missing RUN layers.
Expected behavior
RUN
layers aren't empty.To Reproduce
Steps to reproduce the behavior:
--use-new-run=true
flagAdditional Information
Dockerfile
Build Context
See repository link provided above in the reproduction step.
Kaniko Image (fully qualified with digest)
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: