ric/uptime-kuma
1
0
Fork 0
mirror of https://github.com/louislam/uptime-kuma.git synced 2024-11-23 23:04:04 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Update How-to-Monitor-Docker-Containers.md (#66)

Vic Banana 2023-11-27 05:47:24 -05:00 committed by GitHub
parent abbdec862c
commit d0413ea29f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -83,6 +83,13 @@ Add a new Docker host and choose TCP as the option. Specify the IP address of th
![Docker host monitor](img/docker-host.png) ![Docker host monitor](img/docker-host.png)
**Configuring certificates for Docker TLS connection**
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/`.
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)`.
## Related Discussion ## Related Discussion
- https://github.com/louislam/uptime-kuma/issues/2061 - https://github.com/louislam/uptime-kuma/issues/2061