"Dolce" sends notifications for docker container events

I found a cool docker image named dolce that will monitor docker and send notifications when containers change status. It supports email, discord, telegram and more. I am using it with Gmail and an app password.

https://dangrie158.github.io/dolce/latest/

My docker run command looks like this, and monitors all containers running on my host.

docker run -d \
--name dolce \
--restart unless-stopped \
-v /var/run/docker.sock:/var/run/docker.sock \
-e TZ=Your/Timezone \
-e DOLCE_LOG_LEVEL=INFO \
-e SMTP_FROM="Dolce Container Monitor <<username>@gmail.com>" \
-e SMTP_HOSTNAME=smtp.gmail.com \
-e SMTP_PORT=465 \
-e SMTP_RECIPIENTS=<username>@gmail.com \
-e SMTP_USETLS=1 \
-e SMTP_USERNAME=<username>@gmail.com \
-e SMTP_PASSWORD=**************** \
dangrie158/dolce:v2.10.9

Thx for sharing. Is there any use case for it? I’ve rarely seen docker issues with Storj. Mostly file system or node specific difficulties.

1 Like

For me - none. I do not need any notifications. I did setup them back in 2019 and almost forgot.
Sometimes the satellites sends me that my nodes are offline (the docker ones), but it’s kind of expected - they are running under Docker Desktop for Windows (WSL2 engine), and sometimes the WSL2 engine is hanging (because it’s not updated to a latest version and I hesitate to do so, because it’s an old hardware, it may fail to blue screens with new versions, and I’m aware, that it has a hardware bugs in the CPU and MB, so it’s incompatible with Linux - under Linux it cannot work even 24h without a complete hang, where you need to use a reset button, but I’m far away from this server).
The solution is kind of simple - you need to kill the hanging service, unfortunately only via GUI (the CLI version is rejecting to kill it and demands to have a reboot, which I do not want to perform remotely for obvious reason - it’s Windows, it can die any time), but I have a Wireguard server on my router and can connect via RDP to restart it.

I like knowing when the docker containers restart for any reason. They’re all configured with the restart: unless-stopped directive.

Yesterday morning my nodes were in a crash loop for an unknown reason. I would not have known if I hadn’t logged in to the server and run docker ps and seen their short uptime.

Same as months ago when the test data started, my nodes would crash and docker would automatically restart them because of the unless-stopped directive. Only checking the uptime would show there was an issue.

I advise to use this one. This helps you with regular mailing and optional discord push messages in case of issues, related AND unrelated to docker:

1 Like