On Monday, July 17, 2017, 11:08:06 PM EDT, Mike Jumper <[email protected]> wrote:
> On Mon, Jul 17, 2017 at 7:37 PM, Kaushik Srinivasan > <[email protected]> wrote: >> >> ... >> >> Also there's a major information I might have left out. I have been setting >> all this up in Docker. Not using the docker file provided in the github as >> I'm building on an arm architecture. It needs slightly different settings. >> >Can you share the Dockerfile and/or the images themselves? > Is there anything else custom about your deployment? That the > extension itself was (at least previously) actually modified and not > the version included in the 0.9.13-incubating RC, and that the webapp > is actually running under a custom Docker image, are all pretty > important details. Yeah, I'd have to agree that these changes are fairly important in debugging the problems you're seeing. Based on the Dockerfile you provided, looks like you're running the raspbian Debian variant from January. I'll see what I can do to build up a matching environment and try to reproduce the issues you're seeing in there. Seems that something about this Docker environment is causing the problems you're experiencing. Also, I see one issue in the Dockerfile right off the bat: COPY guacamole-auth-cas-$GUACAMOLE_VERSION-incubating.jar /etc/guacamole/ That should be: COPY guacamole-auth-cas-$GUACAMOLE_VERSION-incubating.jar /etc/guacamole/extensions/ Please make that change and rerun and see what happens. It's a little strange that it's working at all, but I haven't looked much at how the extensions are loaded from the directory, so maybe they work anywhere inside the /etc/guacamole directory?? Mike, any ideas there? -Nick
