[
https://issues.apache.org/jira/browse/GUACAMOLE-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316727#comment-17316727
]
Mike Jumper commented on GUACAMOLE-1318:
----------------------------------------
{quote}
The Glyptodon image belongs to the company that Mike Jumper works for, so he
may be able to comment on those.
{quote}
Yep, those images are very different and were redesigned from scratch:
https://glyp.to/doc/latest/deploying-using-docker-31424656.html
There are probably some principles in the design of those images that it would
be good to look toward applying to the official Guacamole images. The main
things we took a different direction on with the Glyptodon images were:
* Providing a dedicated environment variable for additional properties
([{{ADDITIONAL_GUACAMOLE_PROPERTIES}}|https://glyp.to/doc/latest/glyptodon-guacamole-12813329.html#id-.glyptodon/guacamolev2.x-ADDITIONAL_GUACAMOLE_PROPERTIES])
* Leveraging {{/dev/shm}} for in-memory storage of {{guacamole.properties}}
contents so that sensitive information is not persisted in the image itself
([{{USE_SHM}}|https://glyp.to/doc/latest/glyptodon-guacamole-12813329.html#id-.glyptodon/guacamolev2.x-USE_SHM]).
* Providing a dedicated template file for {{guacamole.properties}} that will
automatically be filtered for environment variables
({{guacamole.properties.docker}}).
* _Not_ providing a {{GUACAMOLE_HOME}} template thing, which has proven
somewhat confusing in practice. Custom bits are expected to be provided via
{{ADDITIONAL_GUACAMOLE_PROPERTIES}} or via per-file volume mounts into
{{/etc/guacamole/extensions}}.
I don't think the Glyptodon images would play nicely with the entirety of
{{/etc/guacamole}} being replaced by a Docker volume mount. Individual
extensions can be mounted on a per-file basis within
{{/etc/guacamole/extensions}}, but users that need an entirely custom
{{GUACAMOLE_HOME}} should instead build a custom image.
> Mapping host folder to /root/.guacamole fails with rm error message
> -------------------------------------------------------------------
>
> Key: GUACAMOLE-1318
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1318
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-docker
> Environment: QNAP QTS 4.5.2.1594
> [~] # docker version
> Client:
> Version: 20.10.3
> API version: 1.41
> Go version: go1.13.15
> Git commit: c52c09e6b8
> Built: Fri Feb 26 03:34:21 2021
> OS/Arch: linux/amd64
> Context: default
> Experimental: true
> Server:
> Engine:
> Version: 20.10.3
> API version: 1.41 (minimum version 1.12)
> Go version: go1.13.15
> Git commit: 4c417df92a
> Built: Fri Feb 26 04:02:45 2021
> OS/Arch: linux/amd64
> Experimental: false
> containerd:
> Version: v1.4.3
> GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b
> runc:
> Version: 1.0.0-rc93
> GitCommit: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
> docker-init:
> Version: 0.19.0
> GitCommit: de40ad0
> Reporter: Oyvind Overby
> Priority: Minor
> Labels: newbie
>
> Attempts to map a host folder to the internal container folder
> {noformat}
> /root/.guacamole{noformat}
> fails with the following error message:
> {noformat}
> rm: cannot remove '/root/.guacamole': Device or resource busy{noformat}
> We have tried to create the instance with guacamole/guacamole and
> guacamole/quadc on several different host computers using both Docker run,
> Docker Compose as well as Portainer. The result is always the same error
> message.
> Using ozru/guacamole image works, so we assume there is a bug in the
> guacamole/guacamole cotainer image.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
