On Thu, May 8, 2025 at 4:23 AM Joachim Lindenberg <[email protected]> wrote:
> Hello, > I build the docker containers out of staging/1.6.0. guacamole-server aka > guacd builds & runs. However guacamole-client builds and reports (docker > compose logs): > guacamole | find: ‘/etc/guacamole/lib’: No such file or directory > It looks like then the container is stuck. > Please make sure you definitely have the latest commits for that container and that it matches up with the Apache git repo - if you're checking out the code directly from the Apache repos, do a "git pull" and make sure it updates as expected. If you have your own fork of the repo, make sure you've pulled in the latest commits from the Apache git repos. > Ok, I created an /etc/guacamole structure with a link to > /opt/guacamole/extensions, guacamole.properties, and an empty lib > directory. Now guacamole starts, but creates a > GUACAMOLE_HOME is "/tmp/guacamole-home.HLzLUL4L9h", which contains my > properties, but only one extension "Brute-force Authentication > Detection/Prevention". > The new container build process creates a temporary directory and builds things up, and then maps that into the guacamole container. > I have no idea why it creates an (incomplete) copy. > Is this known? Fixed? What branch do you recommend right now? > No, this is not known, and not something that I'm seeing in building from the staging/1.6.0 repo. Please verify the above items and let us know if you're still seeing it. -Nick
