- Server operating system version
- Ubuntu 24.04
- Plesk version and microupdate number
- Plesk Obsidian Web Pro Edition 18.0.66
I am trying to setup some docker services using Plesk Docker Stacks and a local docker-compose.yml located inside webspace directory.
The issue is that the .env file is not picked by docker compose when the extension spins up the custom docker compose command, I have to use `env_file: .env` on each container for it to pick the environment variables the .env contains. This works but the problem with this is now every environment variable inside the .env is exposed in every container, which of course is a security issue, I don't want to expose secrets to containers of other unrelated services. I can make separate .env files for each service, but then my application picks only one .env file which expects all the variables of all the services to live inside.
Can someone confirm that Plesk Docker Stacks is not picking .env file that lives inside the same dir as the docker-compose.yml is located in?
If this is the case, is this an intented behaviour or it should pick the .env file when creating a new Stack?
The issue is that the .env file is not picked by docker compose when the extension spins up the custom docker compose command, I have to use `env_file: .env` on each container for it to pick the environment variables the .env contains. This works but the problem with this is now every environment variable inside the .env is exposed in every container, which of course is a security issue, I don't want to expose secrets to containers of other unrelated services. I can make separate .env files for each service, but then my application picks only one .env file which expects all the variables of all the services to live inside.
Can someone confirm that Plesk Docker Stacks is not picking .env file that lives inside the same dir as the docker-compose.yml is located in?
If this is the case, is this an intented behaviour or it should pick the .env file when creating a new Stack?