Hello Nick,

>>I build the docker containers out of staging/http://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.
 
root@ubuntu:/opt/guacamole-server# git remote -v
origin  https://github.com/apache/guacamole-server.git (fetch)
origin  https://github.com/apache/guacamole-server.git (push)
root@ubuntu:/opt/guacamole-client# git remote -v
origin  https://github.com/apache/guacamole-client.git (fetch)
origin  https://github.com/apache/guacamole-client.git (push)
root@ubuntu:/opt/guacamole-client# git status
On branch staging/1.6.0
Your branch is up to date with 'origin/staging/1.6.0'.

looks ok to me, or what am I missing? Do you recommend a different branch or 
tag?
I got one new commit guacamole-client between yesterday and today, which didn´t 
change the issue.

>>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. 
 
At build time or runtime? At build time seems broken to me. Anyway, the 
container did contain (or start) only one extension, which would also explain 
why others complain TOTP doesn´t work with containers.
Actually I think Guacamole should separate directories for "standard" and 
"custom" extensions in order to facilitate extensions in a docker scenario. 

>>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.

Did you run a docker container at all?

Thanks,
Joachim



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

Reply via email to