You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After setting up a Docker container monitor for my containers I have noticed when my containers crash and go into a restarting loop uptime-kuma will say they are still up
π Reproduction steps
add the docker socket to umptime-kuma
setup a docker container that has restart-always and then starts and crashes so state is constantly starting if you use docker ps
setup a monitor for that container in uptime-kuma
see that is is always up yet the container isn't actually up.
π Expected behavior
For uptime kuma to say the container is down and send a notification
π Actual Behavior
the monitor status continues to say up and I do not get a notification
π» Uptime-Kuma Version
1.23.15
π» Operating System and Arch
ubuntu 22.04
π Browser
google chrome, firefox
π₯οΈ Deployment Environment
Runtime: Docker
Database: sqlite
Filesystem used to store the database on: SSD
number of monitors: 4
π Relevant log output
No response
The text was updated successfully, but these errors were encountered:
π I have found these related issues/pull requests
found nothing
π‘οΈ Security Policy
Description
After setting up a Docker container monitor for my containers I have noticed when my containers crash and go into a restarting loop uptime-kuma will say they are still up
π Reproduction steps
add the docker socket to umptime-kuma
setup a docker container that has restart-always and then starts and crashes so state is constantly starting if you use
docker ps
setup a monitor for that container in uptime-kuma
see that is is always up yet the container isn't actually up.
π Expected behavior
For uptime kuma to say the container is down and send a notification
π Actual Behavior
the monitor status continues to say up and I do not get a notification
π» Uptime-Kuma Version
1.23.15
π» Operating System and Arch
ubuntu 22.04
π Browser
google chrome, firefox
π₯οΈ Deployment Environment
π Relevant log output
No response
The text was updated successfully, but these errors were encountered: