News for hackers. Stuff that matters.

A comment on Optimizing Docker image size and why it matters. Parent comment

Re:Optimizing Docker image size and why it matters by imglorp on Thursday January 06, 2022 @04:38PM (#29830631)
This is huge, thanks for the lead. Others should note it's still experimental and your build command may fail with

> "--squash" is only supported on a Docker daemon with experimental features enabled

Up til now, our biggest improvement was with "FROM SCRATCH".

[ Parent | on HN ]
Re:Optimizing Docker image size and why it matters by gavinray on Thursday January 06, 2022 @04:42PM (#29830676)
No problem.

  > Others should note it's still experimental and your build command may fail with
You might try "docker buildx build", to use the BuildKit client -- squash isn't experimental in that one I believe =)

https://docs.docker.com/engine/reference/commandline/buildx_...

[ Parent | on HN ]
Re:Optimizing Docker image size and why it matters by selfup on Thursday January 06, 2022 @04:42PM (#29830668)
Good to know. `FROM scratch` is such a breath of fresh air for compiled apps. No need for Alpine if I just need to run a binary!
[ Parent | on HN ]
Re:Optimizing Docker image size and why it matters by jrockway on Thursday January 06, 2022 @04:48PM (#29830745)
Do keep in mind that you might want a set of trusted TLS certificates and the timezone database. Both will be annoying runtime errors when you don't trust https://api.example.com or try to return a time to a user in their preferred time zone. Distroless includes these.
[ Parent | on HN ]
Re:Optimizing Docker image size and why it matters by selfup on Thursday January 06, 2022 @06:46PM (#29832393)
Yea CA certs are the first pain point I hit. Worth the hurdle. Noted on the timezone. Never really thought about that one. Thanks!
[ Parent | on HN ]