Docker container monitoring #2433

Closed
opened 2026-02-28 02:54:38 -05:00 by deekerman · 3 comments
Owner

Originally created by @PaulMcF1987 on GitHub (Aug 2, 2023).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I am trying to monitor some Docker containers but having a problem with the Docker Host section

Using Connection type - Socket
I added /var/run/docker.sock:/var/run/docker.sock as a volume on the container
I get the error - connect ENOENT /var/run/docker.sock

When I navigate to /var/run and run the ls command, I get 3 docker items noted - docker, docker.pid & docker.sock

When in the /var/run directory, if I type cat docker.sock it returns cat: docker.sock: No such device or address

Something seems to be getting on the way of docker.sock and am unsure how to remedy this.
Any help would be much appreaciated

📝 Error Message(s) or Log

connect ENOENT /var/run/docker.sock

🐻 Uptime-Kuma Version

latest

💻 Operating System and Arch

Ubuntu 20.04

🌐 Browser

Chrome

🐋 Docker Version

20.0.5

🟩 NodeJS Version

No response

Originally created by @PaulMcF1987 on GitHub (Aug 2, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I am trying to monitor some Docker containers but having a problem with the `Docker Host` section Using Connection type - `Socket` I added `/var/run/docker.sock:/var/run/docker.sock` as a volume on the container I get the error - `connect ENOENT /var/run/docker.sock` When I navigate to `/var/run` and run the `ls` command, I get 3 docker items noted - `docker`, `docker.pid` & `docker.sock` When in the `/var/run` directory, if I type `cat docker.sock` it returns `cat: docker.sock: No such device or address` Something seems to be getting on the way of docker.sock and am unsure how to remedy this. Any help would be much appreaciated ### 📝 Error Message(s) or Log `connect ENOENT /var/run/docker.sock` ### 🐻 Uptime-Kuma Version latest ### 💻 Operating System and Arch Ubuntu 20.04 ### 🌐 Browser Chrome ### 🐋 Docker Version 20.0.5 ### 🟩 NodeJS Version _No response_
deekerman 2026-02-28 02:54:38 -05:00
  • closed this issue
  • added the
    Stale
    help
    labels
Author
Owner

@UptimeKumaBot commented on GitHub (Aug 8, 2023):

Hi, I'm a bot. I'm here to help you to find similar issues: #2248 #2061 #2247 #2139 #2712 #1347

@UptimeKumaBot commented on GitHub (Aug 8, 2023): Hi, I'm a bot. I'm here to help you to find similar issues: #2248 #2061 #2247 #2139 #2712 #1347
Author
Owner

@github-actions[bot] commented on GitHub (Nov 6, 2023):

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

@github-actions[bot] commented on GitHub (Nov 6, 2023): We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 8, 2023):

This issue was closed because it has been stalled for 2 days with no activity.

@github-actions[bot] commented on GitHub (Nov 8, 2023): This issue was closed because it has been stalled for 2 days with no activity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2433
No description provided.