News for hackers. Stuff that matters.

A comment on Kaniko: Build container images in Kubernetes. Parent comment

Re:Kaniko: Build container images in Kubernetes by rckrd on Monday April 16, 2018 @05:01PM (#16852723)
- We've published libraries to interact with the registry without docker or the docker CLI, which we use in these projects

https://github.com/google/go-containerregistry

https://github.com/google/containerregistry

- Our team has built something exactly like you're describing https://github.com/GoogleCloudPlatform/distroless

Dockerfiles without RUN commands are technically more correct: reproducible, much easier to inspect. However, its quite limiting for the existing corpus of Dockerfiles.

I like to think of kaniko as the (pull) + build + push decoupling of the docker monolith. Other tools, like cri-o, have implemented the complement (pull + run).

Disclaimer: I work on kaniko and some of these other tools at Google

[ Parent | on HN ]
Re:Kaniko: Build container images in Kubernetes by leg100 on Tuesday April 17, 2018 @06:58AM (#16857173)
What should one replace the RUN instructions with? Say I have:

`RUN apt-get update` and then an `RUN apt-get install -y pkgX pkgY..pkgN`

I could download each package beforehand, tar em and use docker save, but I'd want the recursive dependency tree of packages too....

[ Parent | on HN ]