Pull, configure and run

Guacamole offers ready-to-run installation packages that are available for Linux distros such as CentOS or Debian. However, the thrust of this article is to illustrate running Guacamole in a Docker container context.

Fire up an environment where you have access to the Docker command line and where you feel comfortable to pull and run Docker images. It’s recommended that you evaluate Guacamole in a sandbox that has Docker tooling installed. The Docker command line should have access to the default registry maintained at hub.docker.com. To verify which registry your Docker tooling is pointing to, type this command:

Scan the output of this command-line tool for Registry and confirm that this field includes index.docker.io (or possibly a mirror of this registry).

The next step is to search for the official Guacamole Docker images using the Docker search command. The search command prints an abbreviated description of the image by default. To receive the full description specify the --no-trunc argument. The search syntax shown below matches various Docker images of Guacamole, including several derivatives. A crude way to filter these results is by stars.

The results should include image guacamole/ guacamole and image guacamole/guacd. To download the Apache Guacamole Proxy image from the Docker Hub registry, execute this command:

Execute the pull command image guacamole/guacamole, as this has the Java and JavaScript bits comprising the Web API and Web UI application layers.