Product Thumbnail

Container Diet

Slim down your Docker images with AI-powered sass. 🐳💅

Open Source
Developer Tools
Artificial Intelligence
GitHub

Stop shipping bloated containers! Container Diet is a CLI tool that analyzes your Docker images and Dockerfiles to provide actionable, context-aware optimization advice. It uses AI to detect unnecessary packages, security risks, and bad practices—all while delivering feedback in a "sassy dietician" persona that makes optimization fun.

Top comment

Hi hunters! 👋 I built Container Diet because I was tired of guessing why my images were 2GB. I wanted a tool that didn't just list layers, but actually understood what I was trying to build and told me how to fix it (with a bit of attitude). Key Features: 🧠 AI-Driven Analysis: Context-aware tips powered by GPT-4o. ⚡ Local-First: Works directly with your local Docker daemon. No pushing required. 🛡️ Security Audits: Catches root users, exposed secrets, and 777 permissions. 🎨 Beautiful UI: Docker-themed CLI with a futuristic web landing page. 💁‍♀️ Sassy Persona: Because optimizing YAML should be entertaining. Hope you like it! Let me know what you think!

Comment highlights

Can we not use other AIs for the same?
Can Container Diet generate images?

Haha, this sounds awesome! 😄 Container Diet not only helps slim down Docker images but does it in a fun, sassy way. Love the idea of AI pointing out unnecessary packages and security risks while making optimization enjoyable!

the context t-aware suggestions save a lot of time. No generic tips, just actual useful pointers.

@k1lgor Love this, making Docker optimisation fun is such a clever angle.
Curious: does Container Diet just analyze the final image, or can it actually suggest alternative base images / multi-stage setups too? That’s where most people’s “container calories” come from.

lol @ "why is this 2GB?" felt. The sassy dietician vibe might actually make me fix stuff instead of shrugging. Love that it's local-only. Curious if it groks multi-stage builds and package manager caches (pip/npm). Tossing it at a chunky image later.

Great ideia! Question, how does is this different from asking Claude or Any model directly? Do have a huge set of rules that you consider best practices? Congrats on the launch