January 10, 20251 yr Why doesn't Docker read the .env file? But if I set the variables inside Docker it accepts them. I already tried chown -R 99:100 chown -R 1001:1000
January 10, 20251 yr Community Expert Solution Docker doesn't look for an env by default, you need to specify that it needs to read one. Turn on advanced view in template, and look for "Extra Parameters", add this to that field, adjusting for the actual path to the env 🙂 --env-file=/mnt/user/appdata/homepage/.env No special permissions required
January 24, 20251 yr Author On 1/10/2025 at 11:53 AM, tjb_altf4 said: Docker doesn't look for an env by default, you need to specify that it needs to read one. Turn on advanced view in template, and look for "Extra Parameters", add this to that field, adjusting for the actual path to the env 🙂 --env-file=/mnt/user/appdata/homepage/.env No special permissions required Is this the same as appdata? Appdata = /mnt/user/appdata/evoapi Edited January 24, 20251 yr by Braulio Dias Ribeiro
January 25, 20251 yr Community Expert 6 hours ago, Braulio Dias Ribeiro said: Is this the same as appdata? Appdata = /mnt/user/appdata/evoapi Its not mandatory to use the appdata path for .envs, but in terms of keeping things organised together, its a neat solution. In my example I've used the appdata folder for homepage to store the .env, so changing it for your example to evoapi is an appropriate change.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.