---
title: "Discussion on \"Docker Image Diet: Find the Problem With dive Before Trying to Fix It\" | Hashnode"
description: "Discussion on \"Docker Image Diet: Find the Problem With dive Before Trying to Fix It\". Don't guess why your Docker image is large — use docker image history and dive to see exactly where the weight is. Fix what's actually broken. A real 1.25GB → 139MB walkthrough."
url: "https://hashnode.com/posts/docker-image-best-practices/69e7d4411b3815358115f28e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Docker Image Diet: Find the Problem With dive Before Trying to Fix It](https://recca0120.hashnode.dev/docker-image-best-practices?utm_source=hashnode&utm_medium=feed)

Don't guess why your Docker image is large — use docker image history and dive to see exactly where the weight is. Fix what's actually broken. A real 1.25GB → 139MB walkthrough.

Apr 21 · 4 min read · recca0120.hashnode.dev  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#dive](https://hashnode.com/tag/dive)
-   [#docker](https://hashnode.com/tag/docker)
-   [#dockerfile](https://hashnode.com/tag/dockerfile)
-   [#optimization](https://hashnode.com/tag/optimization)

## Written by

[recca0120](https://hashnode.com/@recca0120)

@recca0120 · Taipei, Taiwan

  
[View profile](https://hashnode.com/@recca0120)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
