Environment variable DOCKER_TLS_DIR_PATH has no effect

[Merec]

📑 I have found these related issues/pull requests

First implementation:
#2852

Last update:
#3527

Documentation update:
louislam/uptime-kuma-wiki#66

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

The documentation (https://github.com/louislam/uptime-kuma/wiki/How-to-Monitor-Docker-Containers) states the option to overwrite the docker-tls path with the environment variable DOCKER_TLS_DIR_PATH which simply does not work. Looking at the code also reflects that, see last update (#3527) where the reference to process.env.DOCKER_TLS_DIR_PATH has been removed.

I want to mount a read-only directory to the container, containing all relevant certificates for remote docker connections, but mounting onto /app/data/docker-tls results in a not starting container with the message:

chown: changing ownership of '/app/data/docker-tls/example.org': Read-only file system

👟 Reproduction steps

Create a compsoe file, setting the environemnt variable DOCKER_TLS_DIR_PATH

services:
  uptimekuma:
    image: louislam/uptime-kuma:latest
    environment:
      DOCKER_TLS_DIR_PATH: /docker-tls/
    volumes:
      - uptimekuma-data:/app/data
      - docker-certs:/docker-tsl

volumes:
  uptimekuma-data:
  docker-certs:
    external: true

---

👀 Expected behavior

Certificates are looked up in the specified directory

😓 Actual Behavior

DOCKER_TLS_DIR_PATH is ignored and lookup only happens in /app/data/docker-tls

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

Ubuntu 22.04

🌐 Browser

Google Chrome 127.0.6533.73

🖥️ Deployment Environment

• Runtime: Docker version 26.1.4, build 5650f9b
• Database: sqlite
• Filesystem used to store the database on: volume

📝 Relevant log output

No response