From what I gather, QNAP simply does not and has no plan to support .env files as part of a yaml for docker, natively in container station. I did see that if I can create a docker via SSH, and it does show in container station - but none of the GUI really works (no commands, you have to SSH in again to manage the container). I’m not opposed to this, but when I use docker compose with an identical yaml via SSH, it never works quite right - I assume something to do with virtual switch/networking, or possibly storage references that don’t take. I can use the same yaml in container station and it works without issue.
Has anyone else experienced this? I don’t really mind moving the variables into the yaml, but I don’t understand why it doesn’t work successfully. Unfortunately I’m not quite sharp enough w/ docker and linux to figure out where it’s going wrong.
Specifically I’ve tried this w/ Immich: Docker Compose [Recommended] | Immich