By: Lars Van Casteren user 12 Feb 2019 at 3:41 p.m. CST

3 Responses
Lars Van Casteren gravatar
I'm running Gluu CE behind a webproxy using a virtual ip approach but is the virtual IP still a requirement for Gluu Docker Edition? Somehow I was under the impression that using a different nginx host port while the internal docker port remains 443 and also providing the webproxy domain name to oxtrust (through the dockerfile extra_hosts) with the internal docker nginx ip it would work using a single ip on the host but it does not, oxtrust seems to connect to the external web proxy URL. I've tried static ip's for the containers and providing extra_host and while oxtrust nslookup resolves the domain name to the niginx docker IP it somehow does not work, so I'm back to using a virtual ip for the nginx exposed host port 443 binding. Thanks, L

By Isman Firmansyah staff 12 Feb 2019 at 7:27 p.m. CST

Isman Firmansyah gravatar
Hi Lars, The `extra_host` is optional. It was meant for deployment that using non-resolvable public domain. For example, in local development we're using madeup domain name that mapped to host `/etc/hosts` file. Thanks,

By Michael Schwartz staff 12 Feb 2019 at 10:03 p.m. CST

Michael Schwartz gravatar
There is no community support entitlement for Gluu Server Docker Edition. Also, in th future the license itself for Gluu Docker containers will be moved to GLUU-SUPPORT.

By Lars Van Casteren user 13 Feb 2019 at 2:16 a.m. CST

Lars Van Casteren gravatar
Hi, thanks for you reply. I understand, we'll work something out through pm. Gr, L