Issue #1206: Allow initial docker bake build to use custom IP.

Author: geerlingguy

docs/other/docker.md

@@ -4,11 +4,27 @@ Drupal VM includes a few `composer` scripts and an example `docker-compose.yml`
 
 > **Docker support is currently experimental**, so you may want to wait until Docker support is more finalized unless you're already familiar with Docker, and okay with potentially backwards-incompatible changes when upgrading Drupal VM.
 
+## Managing your hosts file
+
+Before using Docker to run Drupal VM, you should [edit your hosts file](https://support.rackspace.com/how-to/modify-your-hosts-file/) and add the following line:
+
+    192.168.88.88  drupalvm.dev
+
+...but substituting the IP address and domain name you'd like to use to access your Drupal VM container.
+
+> If you're using Docker for Mac, you need to perform one additional step to ensure you can access Drupal VM using a unique IP address:
+>
+>   1. Add an alias IP address on the loopback interface: `sudo ifconfig lo0 alias 192.168.88.88/24`
+>
+> Note that you'll have to create the alias again after restarting your computer. See [this Docker (moby) issue](https://github.com/moby/moby/issues/22753#issuecomment-246054946) for more details.
+
 ## Building ('baking') a Docker container with Drupal VM
 
 After you've configured your Drupal VM settings in `config.yml` and other configuration files, run the following command to create and provision a new Docker container:
 
-    composer docker-bake
+    [OPTIONS] composer docker-bake
+
+Look at the variables defined in the `provisioning/docker/bake.sh` file for all the currently-available options (e.g. `DRUPALVM_IP_ADDRESS`, `DISTRO`, etc.). You can use Drupal VM's defaults by running the `composer docker-bake` command without any options.
 
 This process can take some time (it should take a similar amount of time as it takes to build Drupal VM normally, using Vagrant and VirtualBox), and at the end, you should see a message like:
 
@@ -51,12 +67,3 @@ Drupal VM includes an `example.docker-compose.yml` file. To use the file, copy i
     docker-compose up -d
 
 (The `-d` tells `docker-compose` to start the containers and run in the background.) You can stop the containers with `docker-compose stop`, or remove all their configuration with `docker-compose down`.
-
-> If you're using Docker for Mac, you need to perform two manual steps prior to running `docker-compose up` to ensure you can access Drupal VM using a unique IP address:
-> 
->   1. Run `sudo nano /etc/hosts` and add a line for Drupal VM in Docker (e.g. `192.168.88.88  drupalvm.dev` using the defaults).
->   2. Add an alias IP address on the loopback interface: `sudo ifconfig lo0 alias 192.168.88.88/24`
-> 
-> Note that you'll have to create the alias again after restarting your computer. And if you don't know what any of this means, you might want to hold off on running Drupal VM inside Docker for now :)
-> 
-> See [this Docker (moby) issue](https://github.com/moby/moby/issues/22753#issuecomment-246054946) for more details.

provisioning/docker/bake.sh

@@ -6,21 +6,25 @@
 set -e
 
 # Set variables.
+DRUPALVM_IP_ADDRESS="${DRUPALVM_IP_ADDRESS:-192.168.88.88}"
 DRUPALVM_MACHINE_NAME="${DRUPALVM_MACHINE_NAME:-drupal-vm}"
 DRUPALVM_HOSTNAME="${DRUPALVM_HOSTNAME:-localhost}"
 DRUPALVM_PROJECT_ROOT="${DRUPALVM_PROJECT_ROOT:-/var/www/drupalvm}"
 
-HOST_HTTP_PORT="${HOST_HTTP_PORT:-8080}"
-HOST_HTTPS_PORT="${HOST_HTTPS_PORT:-8443}"
+DRUPALVM_HTTP_PORT="${DRUPALVM_HTTP_PORT:-80}"
+DRUPALVM_HTTPS_PORT="${DRUPALVM_HTTPS_PORT:-443}"
 
 DISTRO="${DISTRO:-ubuntu1604}"
 OPTS="${OPTS:---privileged}"
 INIT="${INIT:-/lib/systemd/systemd}"
 
-# Pretty colors.
-red='\033[0;31m'
-green='\033[0;32m'
-neutral='\033[0m'
+# Helper function to colorize statuses.
+function status() {
+  status=$1
+  printf "\n"
+  echo -e -n "\033[32m$status"
+  echo -e '\033[0m'
+}
 
 # Set volume options.
 if [[ "$OSTYPE" == "darwin"* ]]; then
@@ -30,12 +34,12 @@ else
 fi
 
 # Run the container.
-printf "\n"${green}"Bringing up Docker container..."${neutral}"\n"
+status "Bringing up Docker container..."
 docker run --name=$DRUPALVM_MACHINE_NAME -d \
   --add-host "$DRUPALVM_HOSTNAME  drupalvm":127.0.0.1 \
   -v $PWD:$DRUPALVM_PROJECT_ROOT/:$volume_opts \
-  -p $HOST_HTTP_PORT:80 \
-  -p $HOST_HTTPS_PORT:443 \
+  -p $DRUPALVM_IP_ADDRESS:$DRUPALVM_HTTP_PORT:80 \
+  -p $DRUPALVM_IP_ADDRESS:$DRUPALVM_HTTPS_PORT:443 \
   $OPTS \
   geerlingguy/docker-$DISTRO-ansible:latest \
   $INIT
@@ -44,14 +48,13 @@ docker run --name=$DRUPALVM_MACHINE_NAME -d \
 docker exec $DRUPALVM_MACHINE_NAME mkdir -p $DRUPALVM_PROJECT_ROOT/drupal
 
 # Set things up and run the Ansible playbook.
-printf "\n"${green}"Running setup playbook..."${neutral}"\n"
+status "Running setup playbook..."
 docker exec --tty $DRUPALVM_MACHINE_NAME env TERM=xterm \
   ansible-playbook $DRUPALVM_PROJECT_ROOT/tests/test-setup.yml
 
-printf "\n"${green}"Provisioning Drupal VM inside Docker container..."${neutral}"\n"
+status "Provisioning Drupal VM inside Docker container..."
 docker exec $DRUPALVM_MACHINE_NAME env TERM=xterm ANSIBLE_FORCE_COLOR=true \
   ansible-playbook $DRUPALVM_PROJECT_ROOT/provisioning/playbook.yml
 
-printf "\n"${green}"...done!"${neutral}"\n"
-
-printf "\n"${green}"Visit the Drupal VM dashboard: http://localhost:$HOST_HTTP_PORT"${neutral}"\n"
+status "...done!"
+status "Visit the Drupal VM dashboard: http://$DRUPALVM_IP_ADDRESS:$DRUPALVM_HTTP_PORT"