Open vic1707 opened 2 months ago
Looking at the code for a naive workaround or solution I feel like instead of https://github.com/haugene/docker-transmission-openvpn/blob/fd609f2ace1970858d3c32fcbd6c271b3d274d39/openvpn/start.sh#L204 the container could simply do a symlink ?
- cp /run/secrets/openvpn_creds /config/openvpn-credentials.txt
+ ln -fs /run/secrets/openvpn_creds /config/openvpn-credentials.txt
I'll make some tests in the coming days if I can find time.
Is there a pinned issue for this?
Is there an existing or similar issue/discussion for this?
Is there any comment in the documentation for this?
Is this related to a provider?
Are you using the latest release?
Have you tried using the dev branch latest?
Docker run config used
Current Behavior
Everything works fine but when inspecting the content of the config dir mounted locally I realized that it was
And upon reading the content of
openvpn-credentials.txt
&transmission-credentials.txt
I realized that the credentials were in plain text. And as said in the logs:I can understand it being that way when using env vars but when using secrets I feel like those files shouldn't exist.
Expected Behavior
When using secrets the corresponding file containing credentials shouldn't be created as it defies the purpose of using the secrets (
openvpn-credentials.txt
,transmission-credentials.txt
)How have you tried to solve the problem?
Nothing to do on my side i think except mounting
/config/transmission-home
instead of/config
?Log output
HW/SW Environment
Anything else?
I hope I didn't miss any existing issue when looking for it 🙏 I could also be misunderstanding the way secrets work or should be used