survivalful/discord-docker-bot repository overview

⁠🐳 Discord Docker Monitor Bot

Monitor your Docker containers directly from Discord — automatic status updates every 30 seconds, crash alerts, uptime tracking, and full container control via slash commands.

⁠✨ Features

• 📋 List all Docker containers on your host
• 📁 Group containers with dedicated Discord channels
• 🔄 Automatic status updates every 30 seconds
• 🟢 Live status indicators (running, exited, paused, created)
• ⏱️ Uptime display for running containers
• 🚨 Crash alerts — configurable per group channel or a separate alert channel
• ▶️ Start / ⏹️ Stop containers directly from Discord
• 📋 View live logs of any container (last 20 lines)
• 🔒 Read-only channels for regular users
• 🏥 Health check endpoint on :8080/health

⁠🚀 Quick Start

Option A — Docker Run (fastest)

docker run -d \
  --restart unless-stopped \
  -e BOT_TOKEN=your_token \
  -e DOCKER_HOST=tcp://your-host:2375 \
  -e GUILD_ID=your_guild_id \
  -e CATEGORY_NAME="Docker Status" \
  -p 8080:8080 \
  survivalful/discord-docker-bot:latest

Option B — Docker Compose (recommended)

1. Create your .env file:

BOT_TOKEN=your_discord_bot_token
DOCKER_HOST=tcp://your-docker-host:2375
GUILD_ID=your_discord_server_id
CATEGORY_NAME=Docker Status

1. Create your docker-compose.yml:

services:
  discord-bot:
    image: survivalful/discord-docker-bot:latest
    restart: unless-stopped
    env_file:
      - .env
    ports:
      - "8080:8080"

1. Start it:

docker compose up -d

That's it! 🎉

After the bot starts, run /setup in Discord to configure your alert preferences.

⁠🤖 Commands

All commands are slash commands (/).

⁠🚨 Crash Alerts

Configure alert behaviour with /setup:

A crash is detected when a container transitions from running → exited during the 30-second monitoring cycle.

⁠📊 Status Indicators

Running containers also display their uptime (e.g. 2d 4h 15m).

⁠⚙️ Configuration

Alert settings (mode and channel) are saved persistently in settings.json via /setup.

⁠🏥 Health Check

The bot exposes a health check endpoint at:

GET http://<host>:8080/health

Returns 200 OK when the bot is running. Useful for container orchestration or uptime monitoring tools like Uptime Kuma.

⁠⚠️ Security Warning

Port 2375 is unencrypted and unauthenticated. Anyone with network access to that port can control your Docker daemon.

Recommendations:

• Use a firewall to restrict access to port 2375
• Only expose it on a trusted local network
• Consider using Docker socket proxy as a safer alternative
• Never expose port 2375 to the public internet

⁠🛠️ Troubleshooting

Bot starts but no channels are created → Check that GUILD_ID is correct and the bot has Manage Channels permission.

"Cannot connect to Docker" → Make sure the Docker remote API is enabled and DOCKER_HOST points to the right address.

Slash commands don't appear → Make sure the bot has the applications.commands scope. Commands are synced to the guild on startup.

Status stops updating → Restart the container: docker compose restart

Bot is offline in Discord → Check your BOT_TOKEN and verify the bot is still in your server.

No crash alerts received → Run /setup to configure an alert mode — without setup, alerts may fall back to the first available group channel.

⁠🤝 Contributing

Contributions are welcome! Open an issue or submit a pull request on the Git repository⁠.

⁠📄 License

Licensed under GNU GPL v3.0⁠ — free to use, modify and distribute, but changes must stay open-source.

⁠🛠️ Support

• 📧 [email protected]⁠
• 🐙 git.survivalful.de/Survivalful/discord-docker-bot⁠