Container-Mon

Container-Mon is a lightweight monitoring tool that watches Docker container health and sends notifications through Shoutrrr-supported services such as…

  • Infrastructure
  • Monitoring & Logging
  • Other
  • Productivity
  • Tools & Utilities
Container-Mon is a lightweight monitoring tool that watches Docker container health and sends notifications through Shoutrrr-supported services such as Telegram, Discord, or Slack when a container becomes unhealthy.

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.

63/100 Good

Maintained
82last commit 7 days ago
Popular
3772 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
88no serious findings, 2 minor, CI, tests

Based on 4 of 5 factors.

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

GitHub stars
72
Open issues
0
Last commit
2026-11-14
Latest release
v1.1.1
License
MIT
Activity
steady

Checked 7 days ago - source: GitHub (RafhaanShah/Container-Mon)

Resources & Compatibility

Requirements not published yet.

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

First-install notes

  • Install GPU driver before toolkit Before adding the NVIDIA Container Toolkit, make sure the NVIDIA GPU driver is installed on the host. Without it, your container will start but won't be able to use the GPU. source
  • Test the GPU in a tiny container Run a sample CUDA container that calls nvidia-smi to check the toolkit works. If it errors or doesn't list your GPU, the driver or toolkit setup is not ready yet. source
  • Give the app GPU access at startup Start Container-Mon with the GPU flag, like --gpus all for Docker, so it can see the card. Without this flag, the app runs as normal and GPU features are unavailable or fail. source
  • Prerequisites Configure a Shoutrrr-supported notification service (Telegram, Discord, Slack, Teams) with the required API keys before first use. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I safely let Container-Mon inspect Docker containers?

Use a Docker API proxy such as Socket-Proxy instead of directly mapping the Docker socket. Container-Mon only needs read access to the list of running containers.

What should be present on the host before GPU features work?

The NVIDIA GPU driver must be installed on the host before adding the NVIDIA Container Toolkit. Without the host driver, the container may start but cannot use the GPU.

How do I start Container-Mon with GPU access?

Start Container-Mon with a Docker GPU flag such as --gpus all. Without the flag, the app runs normally but GPU features are unavailable or fail.

Answers sourced from docs.nvidia.com, docs.nvidia.com, github.com

Community

Collected 48 days ago - public community threads