-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker secrets are not working #374
Comments
Perhaps this can help: #353 However, let me create a new develop release with proper docs so you can do some validations |
New develop image ready with an updated readme. |
I just checked some things with another guy using Docker secrets. He says it's working fine. Secrets Definition:
So ignore the develop image please, in which Docker secrets will not work atm. Could you validate again with the main image? |
Currently im ill, will do test next week |
Support guidelines
I've found an issue and checked that ...
Description
Hi,
The docker secrets you described in the readme are not the offical way of using it.
And also there are not working.
See also the documentation on https://docs.docker.com/engine/swarm/secrets/
But normally, in a docker swarm you create a secret, in the docker compose you can attach the docker secret to the docker container, and the environment var readout the secret file.
By example leantime (opensource planning tool), solved it in the start up script.
Quick example:
if [[ -n "${LEAN_DB_PASSWORD_FILE}" ]]; then LEAN_DB_PASSWORD=$(cat "${LEAN_DB_PASSWORD_FILE}") export LEAN_DB_PASSWORD fi
Expected behaviour
I can use the docker secrets with FILE__
Actual behaviour
Docker secret is not set, fall back to load .env file and everything is working as expected.
Steps to reproduce
Attach docker secrets
Change one of the env vars to FILE__ (by example database password)
DSMR unable to startup because of no password used for DB
Docker info
Version
6.6.67-v8+ #1833 SMP PREEMPT Fri Dec 20 14:14:15 GMT 2024 aarch64 GNU/Linux
Docker compose
n.a.
Container logs
n.a.
Additional info
No response
The text was updated successfully, but these errors were encountered: