binhex-healarr

Healarr monitors Docker containers for unhealthy status and automatically performs configurable actions (restart, stop, etc.) with retry logic to prevent…

  • Infrastructure
  • Media Applications
  • Media Servers
  • Monitoring & Logging
  • Other
  • Productivity
Healarr monitors Docker containers for unhealthy status and automatically performs configurable actions (restart, stop, etc.) with retry logic to prevent false positives. It supports filtering by container label, environment variable, or name, and includes comprehensive logging.

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.

47/100 Fair

Maintained
72last commit 9 days ago
Popular
187 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

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

GitHub stars
7
Open issues
1
Last commit
2026-11-12
Latest release
1.0.25-01
License
GPL-3.0
Activity
rising

Checked 9 days ago - source: GitHub (binhex/arch-healarr)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set or disable the Soulseek peer port In the soulseek section, set listen_port to a port you can open so other Soulseek peers can connect back to you; set it to 0 to disable the listener. Without an open port, remote peers may not reach you and downloads can be slower or fail, so use 0 only for intentional firewalled mode. source
  • Tell Seakarr manual or batch mode Mode selection is explicit: --artist and --album are manual selectors, --batch-file is a batch selector, and they do not override search.default_mode. If the configured mode is auto, add --mode manual for one artist/album or --mode batch for a list file so Seakarr uses the mode you intended. source
  • Store music in Artist/Album folders Store your music in an Artist/Album folder layout, like /media/music/Artist/Album/track files, and point Seakarr at a persistent folder you back up. This is the default structure Seakarr expects, so tracks stay organized and your library survives app or volume changes. source
  • Provide Docker socket access Healarr must reach the Docker daemon to inspect and act on containers: mount the host Docker socket into the container, or point it at a socket proxy connection URL. source

Fetched 46 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I give Healarr Docker access without directly mounting the Docker socket?

Set DOCKER_HOST to a Docker socket proxy address, and configure the proxy with CONTAINERS=1, POST=1, and ALLOW_RESTARTS=1. Add ALLOW_STOP=1 for stop actions or ALLOW_START=1 for unpause-after-pause actions.

How do I keep Healarr from acting on a short-lived unhealthy state?

Use the retry settings, RETRY_COUNT and RETRY_DELAY, so it verifies the unhealthy state multiple times before running the configured action.

How can I limit which containers Healarr monitors?

Set CONTAINER_LABEL, CONTAINER_ENV_VAR, or CONTAINER_NAME to filter the containers. These filtering options are combined with OR logic.

Can Healarr notify other services when it takes action?

Yes, it can send notifications through Apprise using the APPRISE_NOTIFICATION_SERVICES variable.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads