# Docker-Controller-Bot

Docker-Controller-Bot is a self-hosted infrastructure app. A Telegram bot that gives you control over your Docker containers from a single place, letting you manage containers remotely via Telegram. It is open source and self-hosted, installable on Docker Hub and Unraid.

Canonical page: https://ourlocalhost.com/app/726/docker-controller-bot

## Description

A Telegram bot that gives you control over your Docker containers from a single place, letting you manage containers remotely via Telegram.

## Platform availability

Available on 1 of 9 platforms: Unraid.

## Health score

63/100 (Good), based on 3 of 4 factors.
- Maintained: 86 (last commit 53 days ago)
- Popular: 48 (261 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)

## Links

- GitHub: https://github.com/dgongut/docker-controller-bot
- Docker Hub: https://hub.docker.com/r/dgongut/docker-controller-bot
- Unraid: https://ca.unraid.net/apps/docker-controller-bot-0l1o2vs1tnz15o?q=Docker-Controller-Bot

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/726/docker-controller-bot), the self-hosted and open-source app directory.