For troubleshooting questions, please post in the following format:
Summary
Docker container up and running using the mattermost-preview image ignores volume mapping.
Steps to reproduce
Set up a docker container using Docker Compose and the mattermost-preview image. Map volumes using the .env variables as stated in Mattermost wiki. Run container, nothing appears in mounted volumes, it still uses default generic docker volumes.
Expected behavior
To put my logs and config, etc, into the correct mapped volumes so I can access them.
Observed behavior
Already stated, but here are links to my compose and .env with private info redacted:
Compose file: Hastebin
.env file: Hastebin
I am running this on Ubuntu LTS 22.04 on Docker version 27.1.1, build 6312585. Accessing via reverse proxy hosted by my Synology NAS’s built in reverse proxy server.
My purpose of running this is to use it as an example for my organization in hopes to get them to subscribe to the enterprise edition and implement Mattermost as a members only message forum. I’ve found that if I switch to the team or enterprise image, I cannot access Mattermost at all, this is why I’m using the preview image.