Why Your Docker Container Is 1.2GB When It Should Be 80MB
Docker images can often be larger than necessary, leading to increased deployment times and costs. Common mistakes include using the wrong base image and installing unnecessary development dependencies. By making adjustments such as switching to a minimal base image and utilizing multi-stage builds, image sizes can be significantly reduced without altering application code.
- ▪Docker images can bloat to sizes like 1.2GB when they could be as small as 80MB.
- ▪Using the wrong base image contributes to the majority of image size bloat.
- ▪Installing development dependencies in production images can unnecessarily increase their size.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Medium |
| Canonical URL | https://sandeepbansod.medium.com/why-your-docker-container-is-1-2gb-when-it-should-be-80mb-7b443a90f60f |
| Publication time | Sun, 24 May 2026 08:18:34 +0000 |
| Retrieval time | 2026-05-24T08:37:31.504Z |
| Last seen | 2026-05-24T08:37:31.504Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Zt3u-C1BaQOy |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Why Your Docker Container Is 1.2GB When It Should Be 80MBSaandeep Baansod7 min read·Apr 15, 2026--ListenShareYou run docker images and see it. Your Node.js API image sitting at 1.2GB. Your colleague’s Python service at 1.8GB. A simple Go binary wrapped in a container at 900MB.Press enter or click to view image in full sizeWhy Your Docker Container Is 1.2GB When It Should Be 80MBYou ship it anyway because it works. The app runs fine. But that 1.2GB gets pulled on every deploy, pushed to every environment, stored in your registry, and downloaded by every developer on the team. At some point someone raises a cloud bill and everyone looks confused.I’ve audited production Docker setups across several projects. The same five mistakes appear every single time.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Medium.
Discussion
0 commentsMore from Medium
