Apache Guacamole is a clientless remote desktop gateway. It supports standard protocols like VNC and RDP. We call it clientless because no plugins or client software are required.
Thanks to HTML5, once Guacamole is installed on a server, all you need to access your desktops is a web browser.
Using this image will require an existing, running Docker container with the guacd image, and another Docker container providing either a PostgreSQL or MySQL database.
The name of the database and all associated credentials are specified with environment variables given when the container is created. All other configuration information is generated from the Docker links.
Beware that you will need to initialize the database manually. Guacamole will not automatically create its own tables, but SQL scripts are provided to do this.
Once the Guacamole image is running, Guacamole will be accessible at http://[address of container]:8080/guacamole/
. The instructions below use the -p 8080:8080
option to expose this port at the level of the machine hosting Docker, as well.
docker run --name some-guacamole --link some-guacd:guacd \ --link some-postgres:postgres \ -e POSTGRES_DATABASE=guacamole_db \ -e POSTGRES_USER=guacamole_user \ -e POSTGRES_PASSWORD=some_password \ -d -p 8080:8080 guacamole/guacamole
Linking Guacamole to PostgreSQL requires three environment variables. If any of these environment variables are omitted, you will receive an error message, and the image will stop:
POSTGRES_DATABASE
- The name of the database to use for Guacamole authentication.POSTGRES_USER
- The user that Guacamole will use to connect to PostgreSQL.POSTGRES_PASSWORD
- The password that Guacamole will provide when connecting to PostgreSQL as POSTGRES_USER
.If your database is not already initialized with the Guacamole schema, you will need to do so prior to using Guacamole. A convenience script for generating the necessary SQL to do this is included in the Guacamole image.
To generate a SQL script which can be used to initialize a fresh PostgreSQL database as documented in the Guacamole manual:
docker run --rm guacamole/guacamole /opt/guacamole/bin/initdb.sh --postgres > initdb.sql
Alternatively, you can use the SQL scripts included with the guacamole-auth-jdbc extension from the corresponding release.
Once this script is generated, you must:
guacamole_db
.guacamole_user
.The process for doing this via the psql
and createdb
utilities included with PostgreSQL is documented in the Guacamole manual.
docker run --name some-guacamole --link some-guacd:guacd \ --link some-mysql:mysql \ -e MYSQL_DATABASE=guacamole_db \ -e MYSQL_USER=guacamole_user \ -e MYSQL_PASSWORD=some_password \ -d -p 8080:8080 guacamole/guacamole
Linking Guacamole to MySQL requires three environment variables. If any of these environment variables are omitted, you will receive an error message, and the image will stop:
MYSQL_DATABASE
- The name of the database to use for Guacamole authentication.MYSQL_USER
- The user that Guacamole will use to connect to MySQL.MYSQL_PASSWORD
- The password that Guacamole will provide when connecting to MySQL as MYSQL_USER
.If your database is not already initialized with the Guacamole schema, you will need to do so prior to using Guacamole. A convenience script for generating the necessary SQL to do this is included in the Guacamole image.
To generate a SQL script which can be used to initialize a fresh MySQL database as documented in the Guacamole manual:
docker run --rm guacamole/guacamole /opt/guacamole/bin/initdb.sh --mysql > initdb.sql
Alternatively, you can use the SQL scripts included with guacamole-auth-jdbc.
Once this script is generated, you must:
guacamole_db
.guacamole_user
.The process for doing this via the mysql
utility included with MySQL is documented in the Guacamole manual.
Please report any bugs encountered by opening a new issue in our JIRA.