The stack fails to start due to it not finding information for keys(postgres password etc)Removed: -### EnvironmentRemoved: -Removed: -_No response_Removed: -### Logs or screenshotsCan provide logs and screenshots if needed.Removed: -Removed: -### ChecksRemoved: -Removed: -- ☑ I searched existing issues.Removed: -- ☑ I wrote this report in my own words, except for direct translation if needed.
Show
Docker secrets not usable
Summary
Using docker .env file for storing keys for the various services is highly insecure. Appending _FILE to env variables to read from /run/secrets/etc makes the services unable to start due to missing information.
Docker foundation recommends using docker secrets either via local file(compose) or docker secret create(swarm mode). This allows better security practices for all secure keys.
https://docs.docker.com/compose/how-tos/use-secrets/https://docs.docker.com/engine/swarm/secrets/
Steps to reproduce
generate keys and place into files/docker secrets(NOT .ENV FILE)
append "_FILE" to all env variables relating to securely generated keys, changing the value to match /run/secrets/ location that is mounted within the containers
attempt to start the stack.
The stack fails to start due to it not finding information for keys(postgres password etc)
Logs or screenshots
Can provide logs and screenshots if needed.
Original by Rex
Show
Docker secrets not usable
Summary
Using docker .env file for storing keys for the various services is highly insecure. Appending _FILE to env variables to read from /run/secrets/etc makes the services unable to start due to missing information.
Docker foundation recommends using docker secrets either via local file(compose) or docker secret create(swarm mode). This allows better security practices for all secure keys.
https://docs.docker.com/compose/how-tos/use-secrets/https://docs.docker.com/engine/swarm/secrets/
Steps to reproduce
generate keys and place into files/docker secrets(NOT .ENV FILE)
append "_FILE" to all env variables relating to securely generated keys, changing the value to match /run/secrets/ location that is mounted within the containers
attempt to start the stack.
The stack fails to start due to it not finding information for keys(postgres password etc)
Environment
No response
Logs or screenshots
Can provide logs and screenshots if needed.
Checks
☑ I searched existing issues.
☑ I wrote this report in my own words, except for direct translation if needed.