Tejal Desai
Tejal Desai
Please feel free to send a PR and i can help you get it in.
Hi @paleozogt Thank you for opening an issue and identifying an essential gap! I have added this to our next milestone
@christianbeland i am able to reproduce this error at my end. Looking into it now,.
@christianbeland , i tried your dockerfile on latest master. Looks like this is fixed now. Can you please try, ``` gcr.io/kaniko-project/executor:edge gcr.io/kaniko-project/executor:debug-edge ``` The dockerfile i used is ``` FROM...
okay let me do that. Thanks for confirming so fast
@SaschaSchwarze0, Thanks for all your questions. >The other issue is that it claims to work without filesystem snapshotting at all and I do not understand how it would detect deleted...
> So, we continue with `--snapshotMode=redo` alone, https://github.com/redhat-developer/build/blob/master/samples/buildstrategy/kaniko/buildstrategy_kaniko_cr.yaml#L34. Great improvement. yes! `--snapshotMode=redo` should suffice and be more accurate then `--use-new-run`. Thanks a lot for confirming and all your feedback.
Unfortunately that is the design decision we took. Normally dockerfiles are kept closer to the code. Is there a reason why you have yours in a different directory?
Thanks for the issue @emanuele-leopardi. Looks like this is a bug. We should not be transforming a Job kind manifest.
@lsoica Thanks for the issue. Looks like there is an issue computing the `Hash` for the derived images. Can you please do me a favour and see if this also...