References to "localhost" broken when using Docker on Windows (through VirtualBox)

When working with Docker on Windows, with VirtualBox as a back-end, Docker creates a virtual machine (boot2docker linux image) with its own IP address, and runs the Docker containers on that. However those ports are not mapped to the local (Windows) host machine. So references to https://localhost don’t resolve properly to the running Blockstack tools. Instead, if in a Dockerized environment like that, they need to be able to be configured, to set the IP address of the running boot2docker VM (something like 192.168.99.100).

[jordanvanbergen]

Trying v0.17 now… looks like installing and starting is working better than yesterday:

8147ed9f3210: Pull complete adf24d70b9bf: Pull complete 08ac07a33362: Pull complete 7603a6b7bdde: Pull complete f17c2b896e3d: Pull complete def9d545d15c: Pull complete

Now let’s see… it’s working! So with 0.17.x it’s working now!

[kantai]

Okay – our start.sh script attempts to set up a network bridge to the docker virtualmachine on ports 6270, 8888, and 1337 – it seems like this is failing if the docker virtualmachine already existed. The offending lines of code are over in our packaging repo:

https://github.com/blockstack/packaging/blob/master/blockstack-toolbox-windows/windows/start.sh#L50

I’ll work on this tomorrow – should be easy enough to use vboxmanage to check if the port forwarding is set up on the virtualmachine, and if not, set it up.

Thanks for finding this!