Docker-Controller-Bot

Bot de Telegram: Lleva el control de tus contenedores docker desde un único lugar.

  • Tools & Utilities
Bot de Telegram: Lleva el control de tus contenedores docker desde un único lugar.

Platform availability

Available on 1 of 9 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)

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
87last commit 42 days ago
Popular
48261 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 13 days ago

GitHub stars
261
Open issues
14
Last commit
2026-09-01
Latest release
v5.0.0_RC9c
License
GPL-3.0
Activity
stale

Checked 5 days ago - source: GitHub (dgongut/docker-controller-bot)

Resources & Compatibility

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

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

First-install notes

  • Put the bot on a Docker network When starting the bot with docker run, pass --network=<network-name> so it joins the intended Docker network (a private channel between containers). If you skip this, the bot may start but fail to reach the containers or services it needs. source

Fetched 14 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does the Telegram bot support Docker Compose?

Yes. It automatically recognizes containers created with Docker Compose as a project and presents them grouped. Commands such as /run, /stop, /restart, /delete, /info, and /compose show the project list first.

What deployment setting is recommended for Docker daemon access?

Use network_mode: host so the bot has direct access to the Docker daemon. This configuration is recommended and should not be changed unless you have specific network requirements.

How can the bot reach containers or services on a Docker network?

Start it with docker run and pass --network=<network-name> so it joins the intended Docker network. If you skip this, it may start but fail to reach the containers or services it needs.

Answers sourced from deepwiki.com, github.com, github.com

Community

Collected 7 days ago - public community threads