<![CDATA[Add the Docker addon to monitor containers]]>Hi, I just opened a PR to add the Docker addon to the Uptime Kuma package, allowing to take advantage of the Docker Container monitor type.

969ec343-1f9a-44c8-80b9-57629792284e-image.png
https://git.cloudron.io/cloudron/uptime-kuma-app/-/merge_requests/1

]]>https://forum.cloudron.io/topic/11943/add-the-docker-addon-to-monitor-containersRSS for NodeSat, 18 Apr 2026 20:29:23 GMTWed, 19 Jun 2024 20:51:50 GMT60<![CDATA[Reply to Add the Docker addon to monitor containers on Thu, 20 Jun 2024 13:37:33 GMT]]>Makes sense. Thanks for the insight, I'll close the PR as it's not relevant right now.

]]>https://forum.cloudron.io/post/90145https://forum.cloudron.io/post/90145Thu, 20 Jun 2024 13:37:33 GMT<![CDATA[Reply to Add the Docker addon to monitor containers on Thu, 20 Jun 2024 07:32:56 GMT]]>Ah, I saw the PR first and this thread second (thanks for the PR!). I commented there, but this is a better place to continue the conversation.

The docker addon in Cloudron is way too powerful at the moment. It gives the app access to all containers and it can do whatever it wants with them. This means a bad uptime kuma can nuke all the app and infra containers in the server. This is the reason why we don't really use it much.

We could implement a optional setting for docker addon. This way the user can buy into this risk and then explicitly enable. This setting has to be implemented in Cloudron.

But this said, Cloudron already has a built-in monitor for the server containers. It tracks oom as well as health check.

]]>https://forum.cloudron.io/post/90100https://forum.cloudron.io/post/90100Thu, 20 Jun 2024 07:32:56 GMT