On Fri, Apr 2, 2021 at 9:35 AM tomlawesome <[email protected]> wrote:
> To add -- I have also tried to change GUACAMOLE_HOME to an alternate > directory so that I might be able to then mount guacamole.properties into > it. > > This does not work however (I believe from the docs) because the official > guacamole image has a /root/.guacamole/ folder and guacamole looks for it > first, and if it exists it over-rides any GUACAMOLE_HOME environment > variables. > > I'm really stuck because the official guacamole image does not include > either vi, vim or nano so I'm unsure how to even edit the > guacamole.properties file directly in the container?? > The Docker image interprets the GUACAMOLE_HOME environment variable independently of the web application, using the variable to represent the location of a directory with the structure of GUACAMOLE_HOME that should be used as the basis for the one generated by the image startup process. The directory is used as a template. See: http://guacamole.apache.org/doc/gug/guacamole-docker.html#guacamole-docker-guacamole-home To provide your own guacamole.properties, you need to volume mount your own equivalent of GUACAMOLE_HOME within the container (do not use one of the standard locations for GUACAMOLE_HOME), and point the container's GUACAMOLE_HOME environment variable at that. If you specify any additional environment variables that are supported by the image, those variables will also be taken into account when producing the merged guacamole.properties. Michael Jumper CEO, Lead Developer Glyptodon Inc <https://glyp.to/>.
