Dokploy / Dokploy/dokploy

Show detailed Docker disk usage entries in monitoring

Open
#4,651 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

The Docker Disk Usage card shows high-level totals for Images, Containers, Volumes, and Build Cache, but it does not show which specific entries are consuming the space. When disk usage grows, users still need to leave Dokploy and run Docker CLI commands to understand what can be cleaned up.

Describe the solution you'd like

Expand the existing Docker Disk Usage card with a collapsible breakdown that shows the largest entries under Images, Containers, Volumes, and Build Cache. The details should preserve the current summary chart while making the underlying disk usage easier to inspect from the Monitoring page.

A PR is already open for this implementation: #4573

Describe alternatives you've considered

The current workaround is to run docker system df -v manually on the server and compare the output with the summary card. This is useful but not convenient for users who are already using Dokploy's Monitoring page.

Additional context

The proposed PR continues using Docker's disk usage output, adds parser coverage for the detailed view, keeps the breakdown collapsible, and includes tests plus a screenshot.

Docker Disk Usage details toggle

Will you send a PR to implement it?

Yes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with PR #4573, which implements this feature using Docker's detailed disk usage output. Review its parser coverage, tests, and screenshot, then verify that the existing summary chart remains intact and the detailed breakdown is collapsible for Images, Containers, Volumes, and Build Cache.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
devops, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.