Please help pointing me to where I am doing it wrong.
My only suspicion is I should be using docker secrets but the description of this option says otherwise that I should be able to get the password from the file:
" You can set any environment variable from a file by using a special prepend FILE__.
As an example:
-e FILE__PASSWORD=/run/secrets/mysecretpassword
Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file."
Thanks for a suggestion but I tried that as well, I’ve put a secret in the transmission config dir which is mounted separately and it was the same result.
Or you are saying I need to mount /run/secrets/ as a separate mount explicitly?
[env-init] PASS set from FILE__PASS
[env-init] PASSWORD set from FILE__PASSWORD
but I believe I might have found a bug as the password is not taken as I can’t login with that password and regardless of the text places in the secret1 file the config is the same
ok so either it’s a bug or the file can’t contain clear text and needs to be formatted in some specific way
as I tried populate a user as it senses the user is provided
[env-init] USER set from FILE__USER
as it enables authentication but user field stays empty so suspect same thing is happening with PASS environment
I have not created a secret as I don’t feel the need for it, I just want to have the password in the file not as a docker env.
From what I am reading deploying a secret in the docker is just a way to populate encrypted information to docker container which then no longer encrypted but in clear text.
Great spot, there were no new line but by default there is end of the line added, I’ve used
# echo -n password_in_clear_text > secret
and that gave me text without new line and it’s working now.
Thank you very much for your help.
PS: not sure if it’s worth adding a note in the readme file that env_file needs to be referenced from container and can’t have newline/endline in it, but might help some in future.