As the title says. I build containers for my platforms/clients/myself-selfhosted@home and you would not believe how much smaller you can get your images. Here’s an example when slimming one of my images:
cmd=build info=results status='MINIFIED' by='18.97X' size.original='1.0 GB' size.optimized='55 MB'
That’s a Python app that I didn’t have to do multi-staged build with docker because of the Slim command. And it’s a working version of that app that I’m using today.
Same for one of my flutter apps that I thought it was as small as it could be:
cmd=build info=results status='MINIFIED' by='1.98X' size.original='66 MB' size.optimized='33 MB'
TLDR: slim your container images!! https://github.com/slimtoolkit/slim
Huh, I figured my containers were already as small as I could get them by using compiled go binaries in a distroless container. But it looks like there could still be some gains to be made!
Yep, same thing I found out! Crazy to see my already quite slim image being reduce all that much!
*size.original=‘1.0 GB’ *
I mean… I don’t know what that does, of course, but I would rarely use “quite slim” to describe that :D
“size.original=‘66 MB’ size.optimized=‘33 MB’”
This one’s nice though
Yeah? I meant the 66MB one. The 1GB was an image that I just installed everything necessary to compile my code and run from the same image. I didn’t try to make it “right”. Nice to know I don’t have to worry about it though!
I love go on distroless, that sucker is like <5Mb. Use it all the time for AWS lambdas.