Docker Cleanup

An Unraid plugin for self-hosters that reclaims disk space by pruning unused Docker images on your chosen schedule, notifying you of the space recovered, and…

  • Infrastructure
  • Plugins
  • Tools & Utilities
An Unraid plugin for self-hosters that reclaims disk space by pruning unused Docker images on your chosen schedule, notifying you of the space recovered, and manually removing confirmed leftover Docker volumes.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

41/100 Fair

Maintained
74last commit 41 days ago
Popular
00 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 4 days ago

GitHub stars
0
Open issues
0
Last commit
2026-10-10
Latest release
2026.08.12.5
License
MIT
Activity
stale

Checked 5 days ago - source: GitHub (Yoshiofthewire/Unraid_Docker_Cleanup)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the pelias command first Clone the Docker repository into the folder where you want Pelias to live, then run the one sudo symlink command that installs pelias. You need this helper to control the Docker containers; without it, the build commands won't work. source
  • Set DATA_DIR before building In the project folder's .env settings file, set DATA_DIR to a folder you can keep safe, such as ./data. This tells the build where to store large map data files, so a missing or wrong path can stop the build or scatter files. source
  • Run the build steps in order Run the pelias commands in the listed order: pull images, start Elasticsearch (the search database), create the index, download/prepare/import data, then start the stack. Skipping steps or changing the order can leave the app missing map data or failing to start. source
  • Install In Unraid, go to Settings ▸ Plugins ▸ Install Plugin and paste the .plg URL from the GitHub README to install the plugin. source
  • Install the plugin In Unraid, open Plugins ▸ Install Plugin and paste https://raw.githubusercontent.com/Yoshiofthewire/Unraid_Docker_Cleanup/main/docker.cleanup.plg, then reload the page to finish. source
  • Unraid install Install via Unraid's Plugins menu by pasting the repository's docker.cleanup.plg link. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I install the Docker Cleanup plugin and where are its settings?

In Unraid, open Settings > Plugins > Install Plugin and paste the .plg URL from the GitHub README. The settings appear under Settings > User Utilities > Docker Cleanup.

Will unused but kept Docker images be removed by the scheduled cleanup?

Yes. The scheduled run uses docker image prune -a -f, deleting every image not referenced by a running or stopped container. Those images are re-pulled when needed again.

Does Docker Cleanup delete unused volumes automatically, and how are named volumes handled?

Volumes are never deleted on a schedule; the manual action only removes volumes you confirm after showing the list. Named volumes are excluded unless you enable include named volumes, and anonymous detection uses a 64 lowercase hex-character name heuristic.

What custom cron formats does the schedule field accept?

It accepts only five numeric fields for minute, hour, day of month, month, and day of week. Names and shortcuts such as MON, JAN, @daily, or @reboot are rejected.

Does the scheduled run report how much space was freed?

Yes. It sends an Unraid notification with the space reclaimed after the scheduled image prune.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads