[GUACAMOLE-281] GUACAMOLE_HOME not taken into account during Docker image sanity checks

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.13-incubating
• Component/s: guacamole-docker
• Assignee: Mike Jumper
• Reporter: Mike Jumper
• Created: 24/Apr/17 01:09
• Updated: 11/Nov/18 17:05
• Resolved: 08/May/17 05:36

Description

When the Guacamole Docker image starts up, it performs sanity checks on the provided environment variables, refusing to start if the variables do not pass. One of these checks validates that at least one authentication mechanism is enabled:

FATAL: No authentication configured
-------------------------------------------------------------------------------
The Guacamole Docker container needs at least one authentication mechanism in
order to function, such as a MySQL database, PostgreSQL database, or LDAP
directory.  Please specify at least the MYSQL_DATABASE or POSTGRES_DATABASE
environment variables, or check Guacamole's Docker documentation regarding
configuring LDAP.

This check does not take the changes made through GUACAMOLE-100 into account, however, and users of the Docker images will still see the above error if authentication is configured solely through specifying GUACAMOLE_HOME.

The GUACAMOLE_HOME environment variable should be taken into account when performing these sanity checks.

Issue Links

• is related to: GUACAMOLE-659 Docker Image does not allow default authentication
• relates to: GUACAMOLE-100 Support arbitrary extensions within Guacamole Docker image
• links to: Docker using guacamole-auth-json for authentication