guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Jumper (JIRA)" <>
Subject [jira] [Resolved] (GUACAMOLE-281) GUACAMOLE_HOME not taken into account during Docker image sanity checks
Date Mon, 08 May 2017 05:37:04 GMT


Michael Jumper resolved GUACAMOLE-281.
       Resolution: Fixed
    Fix Version/s: 0.9.13-incubating

> GUACAMOLE_HOME not taken into account during Docker image sanity checks
> -----------------------------------------------------------------------
>                 Key: GUACAMOLE-281
>                 URL:
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-docker
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>             Fix For: 0.9.13-incubating
> 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:
> {code:none}
> 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.
> {code}
> 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.

This message was sent by Atlassian JIRA

View raw message