glyptodon/guacamole-db-mysql is a Dockerized deployment of MySQL, built off Docker's official MySQL image which is automatically initialized with the Apache Guacamole database schema. It is built using the packages provided by Glyptodon Enterprise and made available under the same EULA. It is normally used to provide a MySQL database for a container using the
Start a Guacamole database instance
To start a MySQL instance which is automatically initialized for use with Apache Guacamole:
some-guacamole-db is the name you wish to assign to your container,
guacamole_db is the name of the database that should be created within MySQL, and
guacamole_password are the credentials that Guacamole will be using to authenticate with MySQL.
In addition to the environment variables documented below, all environment variables supported by the official Docker MySQL image are accepted, as the official MySQL image forms the basis of this image.
ACCEPT_EULA environment variable must be set to "Y" to indicate your acceptance of the Glyptodon Enterprise EULA. This Docker image may not be used except under the terms of the EULA.
The name of the database to create and initialized for use with Apache Guacamole. This environment variable is required and ultimately maps to the
MYSQL_DATABASE environment variable of the official MySQL image.
GUACAMOLE_DATABASE variable is provided here for consistency with the other Guacamole-specific variables, but may be omitted if
MYSQL_DATABASE is provided.
The username and password to use for the MySQL database user specific to the Guacamole web application. This pair of variables differ from the
MYSQL_PASSWORD environment variables provided by the official MySQL image in that the created user has limited privileges, being granted only what privileges are absolutely required for Guacamole to run.
GUACAMOLE_PASSWORD are not strictly required, as the user created with
MYSQL_PASSWORD may be used instead, however they are strongly recommended to ensure the Principle of Least Privilege is followed.
Rather than pass data directly in environment variables, a
_FILE suffix may be added to any environment variable supported by this image to force that variable to be read from the named file within the container. As Docker secrets store sensitive data within files beneath
/run/secrets/ within the container, this can be used to load sensitive data from Docker secrets.
For example, to load the username and password for the limited-privilege user specific to the Guacamole web application from Docker secrets: