mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Docker container monitoring #2433
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#2433
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PaulMcF1987 on GitHub (Aug 2, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
I am trying to monitor some Docker containers but having a problem with the
Docker HostsectionUsing Connection type -
SocketI added
/var/run/docker.sock:/var/run/docker.sockas a volume on the containerI get the error -
connect ENOENT /var/run/docker.sockWhen I navigate to
/var/runand run thelscommand, I get 3 docker items noted -docker,docker.pid&docker.sockWhen in the
/var/rundirectory, if I typecat docker.sockit returnscat: docker.sock: No such device or addressSomething 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
@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
@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 8, 2023):
This issue was closed because it has been stalled for 2 days with no activity.