.repo
file into /etc/yum.repos.d/
so the Docker image build has access to the Keeper Connection Manager packages..repo
file so your image doesn't contain your repository credentials.guacamole.properties.docker
file).tomcat
user to any necessary groups or deploying guacamole.war
).guacamole.properties.docker
entrypoint-combined.sh
and entrypoint-guacamole.sh
entrypoints will both check for the existence of an optional /etc/guacamole/guacamole.properties.docker
file. If this file exists, it will be automatically filtered such that environment variables are substituted within the contents of the file. The filtered contents of this file will be written to /etc/guacamole/guacamole.properties
, overwriting the original file, but omitting any properties which remain unset after filtering.guacamole.properties.docker
leverages the envsubst
utility provided by the gettext package. The gettext package must be installed within any Docker container intended to leverage guacamole.properties.docker
./etc/guacamole/guacamole.properties
file exists within a Guacamole-only or combined image containing the following:guacamole.properties
will be generated using this as a template, substituting the values of the DATABASE_HOSTNAME, DATABASE_USERNAME, DATABASE_PASSWORD, LDAP_HOSTNAME, and LDAP_PORT environment variables. If only the DATABASE variables are set, then properties which depend on other values will automatically be omitted:guacamole.properties.docker
can thus be used to provide a completely custom set of configuration options. Your image need only support the options you specifically need.guacamole.properties.docker
to provide configuration options that leverage environment variables, the gettext package is requiredguacamole.properties.docker
would look like the following:guacamole.properties.docker
to provide configuration options that leverage environment variables, the gettext package is requiredguacamole.properties.docker
would look like the following: