3 ms·
This is cool! Thanks for posting. I can see how this is useful if building images is part of your CI process. I’ve been using https://github.com/dminkovsky/kub
by linkmotif 9y ago
This is cool! Thanks for posting. I can see how this is useful if building images is part of your CI process.
I’ve been using https://github.com/dminkovsky/kube-cloud-build https://github.com/dminkovsky/kube-cloud-build to build images on Google Cloud Container Builder. It handles generating Cloud Container Builder build requests based on the images specified in my Kubernetes manifests, which was a big deal for me since writing build requests by hand was a total pain.
- amq 9y agoIf you have CI, you normally shouldn't need something like this.
- rckrd 9y agoThe idea is to not have to maintain separate CI infrastructure in addition to your Kubernetes cluster. Disclaimer: I worked on this kaniko at Google
- CSDude 9y agoThanks for your work really appreciated, but is there any way to cache some layers?
- dlor 9y agoThere should be! We haven't thought too much about it yet, but there's no reason it wouldn't work. We can't reuse the Docker daemon cache because that would imply access to the docker daemon. Discloser - I work on kaniko and other container things at Google.