Skip navigation
I built software to cut docker image sizes by more than 80%.
0:00 / 1:21

I built software to cut docker image sizes by more than 80%.

omkaar

@omkizzy4.3K followers

Visit on X
2,879 likesDownloadOriginal post

353,309 views

I built software to cut docker image sizes by more than 80%. It uses dynamic analysis and and has a LOT more room for improvement. The demo here shows an ETL workflow docker image, cut down from 1.28GB to 193MB (-85%)! If large docker image sizes are becoming a production problem, I'd be happy to explore how we can help.

10 Comments

Comments from the original post on X (Twitter)

  • omkaar's profile picture

    @omkizzy

    Read more:

    65 likes

  • harambe_musk🍌's profile picture

    @harambe_musk

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

    79 likes

  • omkaar's profile picture

    @omkizzy

    dive is awesome!

    7 likes

  • vivekb.eth | w.ai's profile picture

    @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

  • omkaar's profile picture

    @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

  • Adam M. Smith (史亚当)'s profile picture

    @rndmcnlly

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

    10 likes

  • Vasco Lameiras's profile picture

    @vascolameiras

    Interesting, thanks for sharing. I usually settle with distroless

    10 likes

  • omkaar's profile picture

    @omkizzy

    distroless is the next best thing, my tool is more aggressive than distroless

    2 likes

  • Bobai Kato's profile picture

    @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

  • omkaar's profile picture

    @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