[
https://issues.apache.org/jira/browse/GUACAMOLE-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314491#comment-17314491
]
Nick Couchman commented on GUACAMOLE-1318:
------------------------------------------
{quote}
The strange thing here, is that if I don't try to map a host folder to
/root/.guacamole
then Guacamole itself runs just fine and I can log in and connect to my remote
computers.
{quote}
Yes, the Docker image is designed to use the inputs that you give it via Docker
variables to generate its own guacamole.properties file. There is no need to
pass through the configuration directory from the host to the container unless
you have custom configuration items or extensions that are not explicitly
supported by the startup script. If you don't have custom items, just use the
configuration variables and don't worry about passing the folder through.
{quote}
I tried using both the Glyptodon and the ozru guacamole images, and none of
them had this issue (but I ran into other issues).
{quote}
The Glyptodon image belongs to the company that [~mjumper] works for, and I'm
not familiar with the ozru image(s) you mentioned, but they are not associated
with this project.
{quote}
I tried using the GUACAMOLE_HOME environment variable, but I do not understand
how to make it point to a host path.
Can you help with that?
{quote}
Again, if it works without this, is there some reason you're concerned about
using it?
Also, as this is not a bug, but intended behavior, I suggest going (back) to
the mailing list and having this discussion, there - it will get more attention
from a broader range of community members and is the correct place to discuss
support issues that are not bugs, enhancements, etc. If we decide on the
mailing list that some action is required within the code to improve or fix
behavior, we can always re-open this issue and continue that effort, here.
> 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
> Affects Versions: 1.3.0
> 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)
