[ 
https://issues.apache.org/jira/browse/GUACAMOLE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16351256#comment-16351256
 ] 

Michael Jumper commented on GUACAMOLE-374:
------------------------------------------

{quote}
I believe this intentional, as the assumption is that Guacamole Client, guacd, 
and MySQL may all be run in different containers, and even on different hosts 
...
{quote}

Yes, this is correct. And more to the point - it's bad practice to have a 
Docker image which contains multiple distinct services. Each service really 
should be a separate image.

Normally, you would combine the various images into a deployment (if you're 
going 100% Docker) through Docker links, or through exposing their ports and 
explicitly specifying the hostname/port for the required services. If you 
aren't using Docker across the board, this separation gives you the option to 
still use Docker where needed.

It's proper design, not a bug. ;)

> Installing Guacamole with Docker improvements
> ---------------------------------------------
>
>                 Key: GUACAMOLE-374
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-374
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-docker
>    Affects Versions: 0.9.13-incubating
>         Environment: sven@fangorn:~$ docker version
> Client:
>  Version:      17.06.1-ce
>  API version:  1.30
>  Go version:   go1.8.3
>  Git commit:   874a737
>  Built:        Thu Aug 17 22:51:12 2017
>  OS/Arch:      linux/amd64
> Server:
>  Version:      17.06.1-ce
>  API version:  1.30 (minimum version 1.12)
>  Go version:   go1.8.3
>  Git commit:   874a737
>  Built:        Thu Aug 17 22:50:04 2017
>  OS/Arch:      linux/amd64
>  Experimental: false
>            Reporter: Sven Gottwald
>            Priority: Major
>
> I installed guacamole as docker container for the first time. Great software! 
> I followed the guide on 
> [https://guacamole.incubator.apache.org/doc/gug/guacamole-docker.html]. There 
> is a lot of unnecessary work to get the container up and running, here are 
> some suggestions to improve the documentation:
> # The link flag is a deprecated legacy feature of Docker. It may eventually 
> be removed. [Legacy container links 
> |https://docs.docker.com/engine/userguide/networking/default_network/dockerlinks/].
>  It is no problem to get guacamole running with a user defined network.
> # The database should be generated automatically on first run. The user and 
> database could be automatically created by 
> [mariadb|https://hub.docker.com/_/mariadb/].
> # ...You should add mariadb as possible backend.
> # Due to its complexity (three services) you should provide a 
> {{docker-compose.yml}} file for use with 
> [docker-compose|https://docs.docker.com/compose/]. This also creates an user 
> defined network.
> Here is an example {{docker-compose.yml}} for use with mariadb:
> {noformat}
> version: '3'
> services:
>   guacd:
>     image: guacamole/guacd
>     depends_on:
>       - db
>   guac:
>     image: guacamole/guacamole
>     ports:
>       - 8080:8080
>     depends_on:
>       - db
>       - guacd
>     environment:
>       - GUACD_HOSTNAME=guacd
>       - MYSQL_PASSWORD=x
>       - MYSQL_DATABASE=guacamole_db
>       - MYSQL_USER=guacamole_user
>       - MYSQL_HOSTNAME=db
>   db:
>     image: mariadb
>     volumes:
>       - /srv/docker/guacamole-mysql:/var/lib/mysql
>     environment:
>       - MYSQL_ROOT_PASSWORD=x
>       - MYSQL_PASSWORD=x
>       - MYSQL_DATABASE=guacamole_db
>       - MYSQL_USER=guacamole_user
> {noformat}
> I don't know why, but {{GUACD_HOSTNAME}} and {{MYSQL_HOSTNAME}} are needed 
> (maybe a bug?)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to