gurulee Posted August 28 Share Posted August 28 I successfully setup and tested the docker host in UptimeKuma. But when I add monitors for docker name, they all fail with 'Request failed with status code 404' Any help would be greatly appreciated. Quote Link to comment
CorneliousJD Posted August 28 Author Share Posted August 28 21 minutes ago, gurulee said: I successfully setup and tested the docker host in UptimeKuma. But when I add monitors for docker name, they all fail with 'Request failed with status code 404' Any help would be greatly appreciated. Use the IP and port instead. 1 Quote Link to comment
gurulee Posted August 29 Share Posted August 29 19 hours ago, CorneliousJD said: Use the IP and port instead. What is the purpose of the Docker setup and docker monitoring type in Uptimekuma then? Quote Link to comment
CorneliousJD Posted August 29 Author Share Posted August 29 Just now, gurulee said: What is the purpose of the Docker setup and docker monitoring type in Uptimekuma then? I'm not the developer. I do suspect there's an incompatibility in the way unraid handles docker and kumas built in method perhaps. I haven't personally investigated. 1 Quote Link to comment
nerbonne Posted August 29 Share Posted August 29 6 hours ago, gurulee said: What is the purpose of the Docker setup and docker monitoring type in Uptimekuma then? 6 hours ago, CorneliousJD said: I'm not the developer. I do suspect there's an incompatibility in the way unraid handles docker and kumas built in method perhaps. I haven't personally investigated. Docker monitoring works fine for me. One thing you do need to do that is not part of the template is add a read only path for /var/run 1 Quote Link to comment
gurulee Posted September 3 Share Posted September 3 (edited) On 8/29/2024 at 3:36 PM, nerbonne said: Docker monitoring works fine for me. One thing you do need to do that is not part of the template is add a read only path for /var/run So I already had that in my docker template. What resolved it for me was to use the docker container ID in the monitor instead of the docker name. Edited September 3 by gurulee Quote Link to comment
nerbonne Posted September 3 Share Posted September 3 47 minutes ago, gurulee said: So I already had that in my docker template. What resolved it for me was to use the docker container ID in the monitor instead of the docker name. Not sure what name you are trying, but if you use the name of the container as retrieved by this command, it will work: docker ps --format ‘{{.Names}}’ 1 Quote Link to comment
gurulee Posted September 3 Share Posted September 3 3 hours ago, nerbonne said: Not sure what name you are trying, but if you use the name of the container as retrieved by this command, it will work: docker ps --format ‘{{.Names}}’ Turns out using the container ID is no good since it changes when you update the docker. I tried using the name of the docker as it shows on my dockers page in the webui. Quote Link to comment
gurulee Posted September 3 Share Posted September 3 3 hours ago, nerbonne said: Not sure what name you are trying, but if you use the name of the container as retrieved by this command, it will work: docker ps --format ‘{{.Names}}’ Thanks! The docker names must be lower case and match the results of the cmd you provided. 👍 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.