Docker Orphan Cleaner

An Unraid plugin that lists Docker images no container references (orphan images, including superseded pulls) and removes the selected ones in bulk, instead…

  • Infrastructure
  • Plugins
  • Tools & Utilities
An Unraid plugin that lists Docker images no container references (orphan images, including superseded pulls) and removes the selected ones in bulk, instead of one at a time from the Docker tab. Each orphan is classified as pinned, template referenced, compose referenced, tagged or untagged, and only untagged images are selected by default. Dry run is on by default and enforced on the server, deletions are never forced, and a scheduled run only ever removes untagged images past a minimum age. The reclaimable build cache is shown and can be pruned on request.

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.

39/100 Low

Maintained
70last commit 51 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

GitHub stars
0
Open issues
1
Last commit
2026-09-30
Latest release
v2026.09.29.03
License
MIT
Activity
stale

Checked yesterday - source: GitHub (bitcryptic-gw/unraid-docker-orphan-cleaner)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Pick which containers to monitor Set the AUTOHEAL_CONTAINER_LABEL setting to a Docker label (a tag you add to a service/container), or use all only if you want every container watched. If the label does not match, the app ignores the containers you need; if you use all, it may restart things you did not expect. source
  • Mount Docker's control socket Mount Docker's control socket (/var/run/docker.sock) into the container and set restart=always, so it can stay running and talk to Docker. Without that socket, it starts but cannot see unhealthy containers or restart them. source
  • Use health checks and startup delay Add a Docker healthcheck (a simple pass/fail test) to each container you mark for autoheal, and set AUTOHEAL_START_PERIOD if the app needs time to boot. Without a healthcheck the app has no clear sign that something is broken, and without the delay a slow start can be treated as a failure. source
  • Install the plugin Install from Community Applications (Apps tab, search 'Docker Orphan Cleaner'), or manually via Plugins ▸ Install Plugin by pasting the .plg URL from the repository. Requires Unraid 7.0.0 or newer (tested on 7.3.2). The plugin appears as a tile under Settings ▸ User Utilities, where its settings are also configured. source
  • Install Install via Community Applications (Apps tab, search 'Docker Orphan Cleaner') or manually via Plugins ▸ Install Plugin. Requires Unraid 7.0.0 or newer. source
  • Finding the plugin After installation, the plugin appears as a tile under Settings ▸ User Utilities; all settings are on the same page. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I install Docker Orphan Cleaner on Unraid?

Install it from Community Applications by searching for Docker Orphan Cleaner, or manually from Plugins > Install Plugin by pasting the plugin definition URL. It appears under Settings > User Utilities.

Is dry-run mode enforced by the server?

Yes, the server enforces dry run. While it is on, nothing is deleted or pruned, and the plugin only reports what it would do.

Which orphan images are selected for deletion by default?

Only untagged images are selected by default. Pinned images are never deleted in the UI or by a scheduled run, while template-referenced, compose-referenced, and tagged images are not selected by default.

What does a scheduled run do in delete mode?

Scheduled runs default to notify only. If delete mode is enabled, they only touch untagged images and still respect pins and the minimum age.

Can it remove the Docker build cache?

It shows the reclaimable build cache and can prune it on request. The pruning runs asynchronously and requires its own confirmation.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads