From a7e9d3cae2200f13dc109d15cbaf8777b178a398 Mon Sep 17 00:00:00 2001
From: Louis Lam <louislam@users.noreply.github.com>
Date: Mon, 12 Sep 2022 17:29:54 +0800
Subject: [PATCH] Created How to Monitor Docker Containers (markdown)

---
 How-to-Monitor-Docker-Containers.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 How-to-Monitor-Docker-Containers.md

diff --git a/How-to-Monitor-Docker-Containers.md b/How-to-Monitor-Docker-Containers.md
new file mode 100644
index 0000000..75e1a12
--- /dev/null
+++ b/How-to-Monitor-Docker-Containers.md
@@ -0,0 +1,27 @@
+## If you are running Uptime Kuma Docker
+
+By default, a docker container is self-contained, which means Uptime Kuma cannot access your host. You need to bind the /var/run/docker.sock to your container.
+
+### (Method 1) Share docker.sock with Uptime Kuma Container
+
+Command argument:
+```bash
+-v /var/run/docker.sock:/var/run/docker.sock:ro
+```
+
+docker-compose:
+
+```yml
+volumes:
+   - /var/run/docker.sock:/var/run/docker.sock:ro
+```
+
+`:ro` (**r**ead**o**nly) is recommended.
+
+### (Method 2) TCP - Bridge Mode
+
+TODO
+
+## Related Disscussion
+
+- https://github.com/louislam/uptime-kuma/issues/2061#event-7365512787
\ No newline at end of file