RE: Apply theme extension to docker container

[Andy Pattrick]

Hi Mike

If I wanted to try this out do I pull 
https://hub.docker.com/r/mjumper/guacamole/ or do I have to build a docker 
image myself from the source?

Thanks Andy.


From: Andy Pattrick [andy.pattr...@horiba.com]
Sent: 28 September 2016 10:31
To: user@guacamole.incubator.apache.org
Subject: RE: Apply theme extension to docker container

Thanks for the detailed explanation Mike. I understand now. I'll try to give 
that a go when I have a moment.

Cheers Andy.


From: Mike Jumper [mike.jum...@guac-dev.org]
Sent: 27 September 2016 02:06
To: user@guacamole.incubator.apache.org
Subject: Re: Apply theme extension to docker container

On Thu, Sep 22, 2016 at 7:36 AM, Andy Pattrick <andy.pattr...@horiba.com> wrote:
> Hi,
>
> I'm trying to apply the example theme extension jar from this thread
> https://sourceforge.net/p/guacamole/discussion/1110834/thread/be2a6785/ to
> my running guacamole docker container. This is to customise the logo and
> title etc as supported by https://glyptodon.org/jira/browse/GUAC-587
>
> I copy the example jar file to my container /root/.guacamole/extensions/
> using docker cp and I can see the file is there after the copy but nothing
> changes when I reload the web page. I figured that the web server has to be
> restarted somehow to load up the new images and translations.
>
> If I stop and start the docker container then the jar file vanishes from the
> folder.
>
> I tried copying the jar file and then immediately doing a docker commit to
> create my own customised image but again when I run this in a container the
> jar file has vanished!
>
> Does anyone know what I'm doing wrong? Why is the extension jar file
> vanishing? How do I apply the example extension to my docker container?
>

The .jar file is vanishing because the startup script for the
Guacamole Docker container recreates GUACAMOLE_HOME every time the
container starts, auto-generating the configuration and copying in any
required extensions based on the environment variables set when the
container was created.

There are WIP changes which will allow you to define a base
GUACAMOLE_HOME which the Docker container will use as a template prior
to generating its own configuration. You can use that to provide your
own extension(s) or arbitrary config:

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

Those changes will not be making their way to git master until the
release is finally out (we are under code freeze until then), but you
can give them a shot as-is by using branch containing the changes:

https://github.com/mike-jumper/incubator-guacamole-client/tree/docker-guacamole-home

With the above, the "GUACAMOLE_HOME" environment variable can be used
to specify an arbitrary location to be copied into the real
GUACAMOLE_HOME just prior to auto-generating the configuration.
GUACAMOLE_HOME will still be wiped out each time the image starts, but
your custom GUACAMOLE_HOME will remain untouched and will still be
used as a basis. If you mount a local directory within the image and
specify that for GUACAMOLE_HOME, then external changes will be
reflected within the image whenever it is restarted, and things should
be pretty convenient.

- Mike

RE: Apply theme extension to docker container

[Andy Pattrick]

Thanks for the detailed explanation Mike. I understand now. I'll try to give 
that a go when I have a moment.

Cheers Andy.


From: Mike Jumper [mike.jum...@guac-dev.org]
Sent: 27 September 2016 02:06
To: user@guacamole.incubator.apache.org
Subject: Re: Apply theme extension to docker container

On Thu, Sep 22, 2016 at 7:36 AM, Andy Pattrick <andy.pattr...@horiba.com> wrote:
> Hi,
>
> I'm trying to apply the example theme extension jar from this thread
> https://sourceforge.net/p/guacamole/discussion/1110834/thread/be2a6785/ to
> my running guacamole docker container. This is to customise the logo and
> title etc as supported by https://glyptodon.org/jira/browse/GUAC-587
>
> I copy the example jar file to my container /root/.guacamole/extensions/
> using docker cp and I can see the file is there after the copy but nothing
> changes when I reload the web page. I figured that the web server has to be
> restarted somehow to load up the new images and translations.
>
> If I stop and start the docker container then the jar file vanishes from the
> folder.
>
> I tried copying the jar file and then immediately doing a docker commit to
> create my own customised image but again when I run this in a container the
> jar file has vanished!
>
> Does anyone know what I'm doing wrong? Why is the extension jar file
> vanishing? How do I apply the example extension to my docker container?
>

The .jar file is vanishing because the startup script for the
Guacamole Docker container recreates GUACAMOLE_HOME every time the
container starts, auto-generating the configuration and copying in any
required extensions based on the environment variables set when the
container was created.

There are WIP changes which will allow you to define a base
GUACAMOLE_HOME which the Docker container will use as a template prior
to generating its own configuration. You can use that to provide your
own extension(s) or arbitrary config:

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

Those changes will not be making their way to git master until the
release is finally out (we are under code freeze until then), but you
can give them a shot as-is by using branch containing the changes:

https://github.com/mike-jumper/incubator-guacamole-client/tree/docker-guacamole-home

With the above, the "GUACAMOLE_HOME" environment variable can be used
to specify an arbitrary location to be copied into the real
GUACAMOLE_HOME just prior to auto-generating the configuration.
GUACAMOLE_HOME will still be wiped out each time the image starts, but
your custom GUACAMOLE_HOME will remain untouched and will still be
used as a basis. If you mount a local directory within the image and
specify that for GUACAMOLE_HOME, then external changes will be
reflected within the image whenever it is restarted, and things should
be pretty convenient.

- Mike

Re: Apply theme extension to docker container

[Mike Jumper]

On Thu, Sep 22, 2016 at 7:36 AM, Andy Pattrick  wrote:
> Hi,
>
> I'm trying to apply the example theme extension jar from this thread
> https://sourceforge.net/p/guacamole/discussion/1110834/thread/be2a6785/ to
> my running guacamole docker container. This is to customise the logo and
> title etc as supported by https://glyptodon.org/jira/browse/GUAC-587
>
> I copy the example jar file to my container /root/.guacamole/extensions/
> using docker cp and I can see the file is there after the copy but nothing
> changes when I reload the web page. I figured that the web server has to be
> restarted somehow to load up the new images and translations.
>
> If I stop and start the docker container then the jar file vanishes from the
> folder.
>
> I tried copying the jar file and then immediately doing a docker commit to
> create my own customised image but again when I run this in a container the
> jar file has vanished!
>
> Does anyone know what I'm doing wrong? Why is the extension jar file
> vanishing? How do I apply the example extension to my docker container?
>

The .jar file is vanishing because the startup script for the
Guacamole Docker container recreates GUACAMOLE_HOME every time the
container starts, auto-generating the configuration and copying in any
required extensions based on the environment variables set when the
container was created.

There are WIP changes which will allow you to define a base
GUACAMOLE_HOME which the Docker container will use as a template prior
to generating its own configuration. You can use that to provide your
own extension(s) or arbitrary config:

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

Those changes will not be making their way to git master until the
release is finally out (we are under code freeze until then), but you
can give them a shot as-is by using branch containing the changes:

https://github.com/mike-jumper/incubator-guacamole-client/tree/docker-guacamole-home

With the above, the "GUACAMOLE_HOME" environment variable can be used
to specify an arbitrary location to be copied into the real
GUACAMOLE_HOME just prior to auto-generating the configuration.
GUACAMOLE_HOME will still be wiped out each time the image starts, but
your custom GUACAMOLE_HOME will remain untouched and will still be
used as a basis. If you mount a local directory within the image and
specify that for GUACAMOLE_HOME, then external changes will be
reflected within the image whenever it is restarted, and things should
be pretty convenient.

- Mike