By: Sam Park user 11 Oct 2018 at 2:34 p.m. CDT

1 Response
Sam Park gravatar
#### Steps - Clone the gluu-docker repository (https://github.com/GluuFederation/docker-config-init) - `cd examples/single-host/` - `chmod +x run_all.sh` - `./run_all.sh` - Enter in all the info #### Actual The script never gets past `[I] Deploying containers`: ``` ./run_all.sh [I] Preparing cluster-wide configuration [W] Configuration not found in Consul [I] Creating new configuration, please input the following parameters Enter Domain: testing123.com Enter Country Code: US Enter State: CA Enter City: Santa Monica Enter Email: spark@goodrx.com Enter Organization: Test Enter Admin/LDAP Password: blahblahblah Continue with the above settings? [Y/n]y [I] Deploying containers ``` And exit code is 1. #### Expect It to finish and be accessible on port 80/443. Looking at the script, I expect to see more log statements, like `[I] Generating configuration for the first time; this may take a moment`. #### Possible clue I'm not sure the exact cause but I did notice that the `run_all.sh` script may not be compatible with Ubuntu 18.04, which is what my laptop is on. To extract the `HOST_IP`, the script runs `ip route | awk`, but the output format for `ip route` has changed since Ubuntu 16.04. 16.04: ``` ip route get 1 1.0.0.0 via 172.17.0.1 dev eth0 src 172.17.0.2 cache ``` 18.04 ``` ip route get 1 1.0.0.0 via 172.17.0.1 dev eth0 src 172.17.0.3 uid 0 cache ``` Notice the different output formats, which will make the piped command `| awk {print $NF;exit}'` definitely extract the wrong data.

By Isman Firmansyah staff 12 Oct 2018 at 11:26 a.m. CDT

Isman Firmansyah gravatar
Hi Sam, The script is tested on Ubuntu 16.04 only. Note that `gluu-docker` is just an example on how to automate deployment of dockerized Gluu Server. You can modify the script to fit your environment/OS.