Hi Mike,
i found the problem.
i had an docker volume set up:
${BASEDIR}/config:/opt/local:ro
where my custom-branding extension and my guacamole.properties resist:
ls config
extensions guacamole.properties
seems that this is not supported any more in this style, on 1.5.5 it was
still working.
where can i put this files now? Is there a new location for this? Or is
the "mkdir /opt/local" only missing in the Dockerfile?
guacamole@guacamole:/opt$ ls
guacamole java
Thanks,
Tobias
Am 15.02.2025 um 17:41 schrieb Michael Jumper:
Can you send your full docker-compose.yml (redacted as necessary)?
The only issue I see with what you've shown below is that the copy of
guacamole-server is being taken directly from the "staging/1.6.0"
branch and thus will not have the pending changes from previously
mentioned PR:
https://github.com/apache/guacamole-server/pull/573
- Mike
On 2/15/25 1:04 AM, Tobias Feller | OPC wrote:
Hi Mike,
i have testet the staging/1.6.0 (docker), but have some problems to
bring it up.
What i have done...
git clone --single-branch --branch staging/1.6.0 https://github.com/
apache/guacamole-server.git
git clone --single-branch --branch staging/1.6.0 https://github.com/
apache/guacamole-client.git
Customize my working docker-compose.yml file from image:
#image: guacamole/guacd:latest
build:
context: ./guacamole-server
dockerfile: Dockerfile
#image: guacamole/guacamole:latest
build:
context: ./guacamole-client
dockerfile: Dockerfile
docker compose build
both images was build succesful, but after:
docker compose up
the client-image didn't boot up...
guacd | guacd[1]: INFO: Guacamole proxy daemon (guacd)
version 1.6.0 started
guacd | guacd[1]: DEBUG: Successfully bound AF_INET socket to
host 0.0.0.0, port 4822
guacd | guacd[1]: INFO: Listening on host 0.0.0.0, port 4822
*guacamole | find: ‘/opt/local/lib’: No such file or directory
*guacamole exited with code 0
Do i need to customize something in the Dockerfile?
Thanks.
Best regards,
Tobias
Am 15.02.2025 um 08:51 schrieb Michael Jumper:
Well, I'm no longer able to reproduce the issues I was encountering
before. Performance of all protocols seems to be excellent when
using a build with:
* Current "staging/1.6.0" for guacamole-client
* The proposed fixes for guacamole-server:
https://github.com/apache/ guacamole-server/pull/573
Using purely the above (no third-party images), is anyone still
encountering issues? If so, what does your deployment look like in
terms of resources and software?
If not, then we may well be good to go...
- Mike
