README.md

Automation Stack

A comprehensive automation and monitoring solution for Docker. This stack provides Docker event notifications, image monitoring, and automatic container updates through Telegram.

Components

1. Docker Telegram Notifier

• Image: lorcas/docker-telegram-notifier

• Purpose: Sends notifications about Docker container events (start, stop, die, etc.) to Telegram

• Documentation: GitHub Repository

2. Diun

• Image: crazymax/diun

• Purpose: Docker image update notifier that monitors Docker images for updates

• Documentation: Official Documentation

3. Watchtower

• Image: containrrr/watchtower

• Purpose: Automatically updates running Docker containers to their latest version

• Documentation: Official Documentation

Container Images

| Service | Image |

|---|---|

| Diun | crazymax/diun:latest |

| Notifier | lorcas/docker-telegram-notifier:latest |

| Watchtower | containrrr/watchtower:latest |

Security Considerations

⚠️ Docker Socket Access: This stack mounts /var/run/docker.sock to monitor Docker container events. This grants the containers access to the Docker daemon, which requires elevated privileges. Only deploy in trusted networks. For more information, see Docker Security Documentation.

Configuration

1. Create a .env file based on .env.example
2. Set up a Telegram bot using @BotFather
3. Get your chat ID (you can use @userinfobot)
4. Configure the schedule for updates in the compose file

Environment Variables

• TELEGRAM_BOT_TOKEN: Your Telegram bot token from @BotFather
• TELEGRAM_CHAT_ID: Your Telegram chat ID
• DOCKER_DATA_BASEFOLDER: Base directory for persistent data (default: /opt/docker/data)

Usage

1. Configure your environment variables

2. Deploy the stack:

   docker compose up -d

Maintenance

The stack is configured to:

• Run Watchtower updates every Monday, Wednesday, and Friday at 1 PM
• Check for image updates every 6 hours with Diun
• Send notifications for all Docker events
• Automatically restart services if they fail