cooperation request
- Langage dominant
- Go
- Étoiles
- 300
- Forks
- 64
- Merge moyen
- 20 min
- PR mergées (30 j)
- 1
Description
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 🙇
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par examiner la configuration préliminaire de envbuilder et le code source de kaniko autour de l’option existante --materialize et de l’option ForceUnpack correspondante. Comparez les options manquantes ou nommées différemment décrites dans l’issue, puis définissez le périmètre de l’intégration et les critères d’acceptation avant d’envisager l’implémentation.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- docker, go, kubernetes
- Domaine
- build-system, devops, infrastructure
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 15/100