mirrors/uptime-kuma
1
0
Fork 0
mirror of https://github.com/louislam/uptime-kuma.git synced 2024-11-22 09:26:05 +03:00
Code Issues Projects Releases Packages Wiki Activity

Improve Docker Host TLS Wiki relate to #4426 and Add Troubleshooting IPv6 for Docker (#95) 

* Improve Docker Host TLS Wiki relate to #4426

* Add Troubleshooting for IPv6 for Docker.

---------

Co-authored-by: Colgrave <hanqixu.blogs@simplelogin.co>
Colgrave 2024-10-09 14:04:12 +08:00 committed by GitHub
parent f4456520a9
commit 354573c0d5
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
How-to-Monitor-Docker-Containers.md

@ -87,6 +87,11 @@ Add a new Docker host and choose TCP as the option. Specify the IP address of th
Assuming you have already properly configured your remote docker instance to listen securely for TLS connections as detailed [here](https://docs.docker.com/engine/security/protect-access/#use-tls-https-to-protect-the-docker-daemon-socket), you must configure Uptime-Kuma to use the certificates you've generated. The base path where certificates are looked for can be set with the `DOCKER_TLS_DIR_PATH` environmental variable or defaults to `data/docker-tls/`. Assuming you have already properly configured your remote docker instance to listen securely for TLS connections as detailed [here](https://docs.docker.com/engine/security/protect-access/#use-tls-https-to-protect-the-docker-daemon-socket), you must configure Uptime-Kuma to use the certificates you've generated. The base path where certificates are looked for can be set with the `DOCKER_TLS_DIR_PATH` environmental variable or defaults to `data/docker-tls/`.
For running uptime-kuma inside docker, mount the parent directory to `/app/data/docker-tls`.
```
-v /docker-cert:/app/data/docker-tls
```
If a directory in this path exists with a name matching the FQDN of the docker host (e.g. the FQDN of `https://example.com:2376` is `example.com` so the directory `data/docker-tls/example.com/` would be searched for certificate files), then `ca.pem`, `key.pem` and `cert.pem` files are loaded and included in the agent options. File names can also be overridden via `DOCKER_TLS_FILE_NAME_(CA|KEY|CERT)`. If a directory in this path exists with a name matching the FQDN of the docker host (e.g. the FQDN of `https://example.com:2376` is `example.com` so the directory `data/docker-tls/example.com/` would be searched for certificate files), then `ca.pem`, `key.pem` and `cert.pem` files are loaded and included in the agent options. File names can also be overridden via `DOCKER_TLS_FILE_NAME_(CA|KEY|CERT)`.

4
Troubleshooting.md

@ -26,3 +26,7 @@ Examples:
curl https://google.com curl https://google.com
ping google.com ping google.com
``` ```
### IPv6
If you are running Uptime Kuma on top of Docker and the service can only be access via IPv6. Please follow the Docker's [official wiki](https://docs.docker.com/config/daemon/ipv6/) to enable IPv6 support.
IPv6 are not supported out of the box on Docker.