Open robflate opened 4 years ago
Hi @robflate,
the listed images are all built upon the same base image:
This behavior is due to the rootfs/etc/cont-init.d/10-vnc-password.sh in GUI Base Image (jlesage/baseimage-gui). At Line 21 you can see that the input of x11vnc -storepasswd command is taken from the environment variable $VNC_PASSWORD that means:
The only way I can see to fix this issue is to raise a Pull Request for the jlesage's Base GUI Image introducing a new env variable called "VNC_PASSWORD_FILE" or modify the script "10-vnc-password.sh" introducing the ability to read from a path if detected inside the env variable "VNC_PASSWORD".
GZ
Thanks for the explanation. Really appreciate it. So the way the repo currently is, the jlesage images have no VNC passwords set?
Hi @robflate,
jleasege images have no VNC password set if you use Docker Secrets, you can still use the .env file as workaround.
I will try to raise a pull request for jlesage/baseimage-gui adding the VNC_PASSWORD_FILE as env variable.
GZ
I can't seem to get secrets working on some containers. E.g.;
Before using secrets the above containers would require a password before opening,
VNC_PASSWORD: $HANDBRAKE_VNC_PASSWORD
After replacing the above with,
VNC_PASSWORD_FILE: /run/secrets/handbrake_vnc_password
and addinghandbrake_vnc_password
as a secret to the container and mounting the file in the stack, the container no longer requires a password.If I change
VNC_PASSWORD_FILE
toVNC_PASSWORD
the password is set to/run/secrets/handbrake_vnc_password
as a string rather than the contents of the file.Other secrets are working correctly and I get no errors on docker up so I'm pretty sure they are setup correctly. Any advise appreciated, thanks.