I expanded the stack by adding adding a web proxy container, to mimic our production traffic routing locally. We have traditionally run ruby and nodejs services on our macs, and connected to virtualized databases, which now run in containers.
Update: This workaround is no longer necessary as of Docker for Mac version 17.06, which provides a special Mac-only DNS name, which resolves to the internal IP address used by the host.Ī few months ago, I built out a docker-compose-based local development environment for our dev team who had been using a long-in-the-tooth vagrant-based environment to run backend databases.
