I built software to cut docker image sizes by more than 80%.
@omkizzy4.3K followers
353,309 views
10 Comments
Comments from the original post on X (Twitter)

@omkizzy
Read more:
65 likes

@harambe_musk
This tool could come in handy for exploring layers of docker that can be shrinked:
79 likes

@omkizzy
dive is awesome!
7 likes

@notorious_VB
this is a common issue we face when running production containers on GPUs, we don’t even have a model in the image just a lot of dependencies. cool stuff would love to check it out
25 likes

@omkizzy
thats the biggest problem with ML dependencies, they are extensible and bloated + dependencies creates a hoard of unused package. static analysis can only get you so far. would love to chat more if this is a pressing problem. Here is a quick explainer -
64 likes

@rndmcnlly
The idea of watching for which parts of the FS are actually touched during execution reminds me of @playablequotes /
10 likes

@vascolameiras
Interesting, thanks for sharing. I usually settle with distroless
10 likes

@omkizzy
distroless is the next best thing, my tool is more aggressive than distroless
2 likes

@bobaikato
Simply reducing the size of the Docker image and confirming that it “still works fine” is not sufficient to guarantee that the image is free of defects. Could you provide more details on the additional testing methods you have used to validate its functionality and stability?
8 likes

@omkizzy
good question, the ETL tool minimal image did precisely the same transformations as the larger image. For images with broader scope, tests on the application are needed to validate whether functionality is working. luckily, most orgs have tests like this. did you have any other ideas?
2 likes