coder
cooperation request
Hi @johnstcn 👋
I'm Martin, the maintainer of the https://github.com/osscontainertools/kaniko community fork. I wanted to reach out to you to ask whether you would be interested in a cooperation on the kaniko source? We do use coder (with envbuilder) internally in my company, as such I have a bit of experience with using kaniko in this very special use-case and I think kaniko is indeed the best fit to prep an environment like this. I would like to add full support for your use-case to kaniko, I added a --materialize option (corresponds to your ForceUnpack option) previously already with that in mind, s.t. we could maybe merge the two forks together and combine our efforts going forwards. Would you be interested in such a cooperation?
I have a preliminary setup that tries to build from our fork here https://github.com/mzihlmann/envbuilder There are still a few options missing, some have different names, but all in all I think it would not be too much effort to integrate your use-case fully.
Thank you for your consideration 🙇
Hi Martin, thank you for getting in touch!
Our custom fork of Kaniko has a bunch of features we adapted specifically for our own use-cases (mainly around reproducibility of image builds from a given set of inputs). I'd personally like to be able to get rid of our custom fork.
From what I can tell, the fork of Kaniko under chainguard-dev seems to mainly be "stable", with mostly security fixes being merged. Is there any relation between that project and osscontainertools/kaniko, or are they completely separate projects?
I was skimming through the code diff and found some real treasures 😃. For example what you have implemented as "cache probing" I'm currently trying to implement as the clumsily titled "multi-stage cache lookahead" here. Also secret mounts, I was hesitant to implement them as they are not really secure in any way, but why not offer the api to the users. If it is ok with you I'll open a few PRs on our side to bring those features in.