I just looked into this and can confirm that the Docker entrypoint for the "guacamole/guacamole:1.6.0-RC1" image is missing existence checks for GUACAMOLE_HOME/lib, producing an error when the GUACAMOLE_HOME template functionality is used (the mechanism for including custom extensions).

This is a regression. I've opened an issue to address this in our next RC:

https://issues.apache.org/jira/browse/GUACAMOLE-2076

- Mike

On 5/20/25 10:58 AM, Joachim Lindenberg wrote:
Hi Nick,

Have you been able to test this in the meantime?

Thanks,

Joachim

*Von:*Nick Couchman <vn...@apache.org>
*Gesendet:* Montag, 12. Mai 2025 13:31
*An:* user@guacamole.apache.org
*Betreff:* Re: Now up for final testing: 1.6.0-RC1

On Sun, May 11, 2025 at 4:19 AM Joachim Lindenberg <guacam...@lindenberg.one.invalid <mailto:guacam...@lindenberg.one.invalid>> wrote:

    Hi Nick,
    Thanks for the answer.
     >This resulted in a Guacamole interface at http://
    guac.domain.local:8080/guacamole <http://guac.domain.local:8080/
    guacamole> with a default login of guacadmin/guacadmin. I'll re-test
    the process with the latest Docker version >and verify, but not
    seeing any issues in my environment.
    Afaik that doesn´t use any extension, correct?
    My authentication is based on a custom extension.
    Joachim

Ah! I missed that detail, very sorry about that. I have _not_ tried to add my own custom extension. I'll have to see if I can come up with a way to test that out.

-Nick



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org

Reply via email to