In my Dockerfile I am using the following: FROM guacamole/guacamole:1.0.0
ADD https://software.lindenberg.one/backup/downloads/guacamole-lindenberg-backup-1.0.0.jar /etc/guacamole/extensions/ COPY guacamole.properties /etc/guacamole/ The disadvantage is that I need to rebuild for any configuration change. I did that already with pre 1.0 and ignoring https://issues.apache.org/jira/browse/GUACAMOLE-464 . You may want to prefer environment variables. I was also considering to just map /etc/guacamole/extensions/ to a host directory, as then multiple extensions (in particular versions of my own during development) would not multiply the number of docker images, but that kind of requires a contract from Guacamole team that there is never a “standard extension” or similar in that location by default. Best Regards, Joachim Von: Nick Couchman <vn...@apache.org> Gesendet: Thursday, 23 April 2020 17:06 An: user@guacamole.apache.org Betreff: Re: Login Page customization. On Thu, Apr 23, 2020 at 10:50 AM Riano De Souza <riano.deso...@mrj.co.za <mailto:riano.deso...@mrj.co.za> > wrote: Cool so I got the extention template and so on. But where is the extentions folder located? And wont it just get overwritten when the container gets reloaded? You'll probably have to modify the startup script for the container to pull in the custom branding extension prior to starting Tomcat. My Docker skills are not all that complete, so I can't tell you without some trial-and-error exactly how you'd accomplish that, but I know that you can specify custom startup commands for containers after you deploy them, so I'd guess you just want to make sure you deploy that extension every time. Also, I believe the extension would only be overwritten if you reload the container from the original image - I would think it would persist between starts and stops. I could be wrong about that, though - like I said, my Docker familiarity is a bit sketchy. Maybe others on the list can offer their experiences and advice :-). -Nick