[GH-ISSUE #1893] Docker - Volume mapping documentation #1177

New issue

Open

opened 2026-03-02 02:21:41 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 02:21:41 +03:00

Owner

Originally created by @mr6volt on GitHub (Jun 16, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1893

When looking at the Docker documentation for installation, I noticed that it appears to be missing instructions for creating folders on the host to map the persistent volume ENV entries. I only discovered this by downloading and reading the compose file that there was consideration for persistent storage at all.

The documentation needs to be updated to include information about creating folders on the host, and WHY it is important to do so. (I assume the update process requires the container to be torn down and replaced with a newly pulled image?)

Also, the SSL certificates shouldn't base64-ed into the environment variables. I think it would be better to instead be made available via a persistent folder. Thus allowing easy renewals using a command prompt on the host and a docker container restart if required.

Originally created by @mr6volt on GitHub (Jun 16, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1893 When looking at the Docker documentation for installation, I noticed that it appears to be missing instructions for creating folders on the host to map the persistent volume ENV entries. I only discovered this by downloading and reading the compose file that there was consideration for persistent storage at all. The documentation needs to be updated to include information about creating folders on the host, and WHY it is important to do so. (I assume the update process requires the container to be torn down and replaced with a newly pulled image?) Also, the SSL certificates shouldn't base64-ed into the environment variables. I think it would be better to instead be made available via a persistent folder. Thus allowing easy renewals using a command prompt on the host and a docker container restart if required.