[Idea] Allow configurable paths for ACME and access log files

[xd003]

What problem does this solve?

Traefik Manager currently expects the Traefik ACME and access log files to be mounted at fixed paths:

- /path/to/traefik/acme.json:/app/acme.json:ro
- /path/to/traefik/logs/access.log:/app/logs/access.log:ro

This works well with bind mounts, but is awkward when i have configured Traefik to store its certificates and logs in Docker named volumes.
A named volume can be mounted into Traefik Manager, but Docker mounts it as a directory rather than allowing an individual file from that volume to be mounted directly at /app/acme.json or /app/logs/access.log.

Proposed solution

Allow the paths to the ACME file and access log file inside the Traefik Manager container to be configurable, preferably through environment variables.
For example:

environment:
  ACME_FILE_PATH: /traefik-certs/acme.json
  ACCESS_LOG_PATH: /traefik-logs/access.log

volumes:
  - traefik_certs:/traefik-certs:ro
  - traefik_logs:/traefik-logs:ro

This would allow users to mount existing Traefik named volumes as directories and point Traefik Manager to the actual files within those volumes, while keeping the current paths as defaults for backward compatibility.

Alternatives you've considered

No response

Which area does this relate to?

Other

Additional context

Ideally the existing defaults would remain:

ACME_FILE_PATH=/app/acme.json
ACCESS_LOG_PATH=/app/logs/access.log

so existing deployments would require no changes.

[chr0nzz]

This already works - the variables just have slightly different names than you guessed.

ACME_JSON_PATH and ACCESS_LOG_PATH are both supported, and their defaults are already the ones you want, so existing deployments need no changes.

Your example becomes:

environment:
  ACME_JSON_PATH: /traefik-certs/acme.json
  ACCESS_LOG_PATH: /traefik-logs/access.log

volumes:
  - traefik_certs:/traefik-certs:ro
  - traefik_logs:/traefik-logs:ro

I tested that exact shape - a volume mounted as a directory with the file inside it - and both resolve. The read guard adds the directory named by each variable to its allow list, so a path outside /app is fine.

Both can also be set in Settings, under Certificates and Logs respectively, which takes precedence over the environment variable if you'd rather not restart the container to change them.

Remote agents take the same two variables, so the same applies there.

Documented in Environment Variables.

[xd003]

Thanks for the detailed reply, and my bad, i missed that there's a dedicated environment variables section.

I’m just starting out and was looking at the Traefik-related environment variables on this page: https://traefik-manager.xyzlab.dev/docker.html. Since options for the static config file and dynamic config file/directory were listed there, I assumed this variable would be listed here too if it was supported.

[chr0nzz]

Added a Named volumes section to the Docker docs and to both variables in the env-var reference, since every example showed a bind mount and it read as though the paths were fixed. That ships with v1.13.0.