Docker Toolbox - Localhost not working

Question

So I'm using Docker Toolbox because I don't have Hyper-V on my machine since it's not Windows 10 pro. Everything seems to work fine, but when I try to go on my browser 0.0.0.0:80 it always returns me: This site can’t be reached

But when I run the command: docker container ps I get the following: 0.0.0.0:80->80/tcp meaning that this address should work. I searched across stackoverflow and github issues. Now I'm stuck.

Am I missing something?

Thanks, Mark

EDIT:

Using docker-machine ip default returns me 192.168.99.100. I run that on port 80. I still get the same result except that the address becomes the container id: https://fd677edg12

I run that command on cmd to find my ipv4: cmd /k ipconfig /all. Put the result with the port and it returns the same thing: https://fd677edg12

Answer 1

Docker Toolbox doesn't get as many conveniences as Docker for Windows, but you're correct in using it since you're on Home edition.

In Toolbox, nothing will be localhost, and will be 192.168.99.100 by default, since it's running a Linux VM in VirtualBox.

So if you run docker run -p 80:80 nginx

(notice I had to publish a port for 192.168.99.100 to listen on that port)

Then going to http://192.168.99.100 should work.

Answer 2

I initially had a few issues with accessing my Applications at localhost:8080 while using DockerToolBox and OracleVM VirtualBox.

In VirtualBox:

1. Click the appropriate machine (probably the one labeled "default")
2. Settings
3. Network > Adapter 1 > Advanced > Port Forwarding
4. Click "+" to add a new Rule
5. Set Host Port 8080 & Guest Port 8080; be sure to leave Host IP and Guest IP empty

Run the command:

docker run -p 8080:8080 ${image_id}

Answer 3

I was following docker for windows tutorial in https://docs.docker.com/docker-for-windows/#set-up-tab-completion-in-powershell and got stuck in step #6 when test nginx in the web browser. Seems I faced a similar problem since I also use Windows Home and don't have Hyper-V. My workaround is quite simple:

1. check your docker IP default

$ docker-machine ip default

192.168.99.100

2. Go to Oracle Virtual Machine to set for port forwarding. Make sure the network setting is NAT, and add port forwarding. Host IP: 127.0.0.1, Guest IP: 192.168.99.100, port all set to 80 like this

3. Try again to your browser and run http://localhost or http://127.0.0.1 (can add the port 80 also). It should run.

The thing is that the nginx IP is meant to be accessible within the docker Virtual Machine, so that we need that port forwading setting in order to access it directly in the host machine's browser

Answer 4

You can use localhost instead of '192.168.99.100' by following the instructions:

Step #01:

docker-machine ip default

You will see the default IP

Step #02:

docker-machine stop default

Step #03:

1. Open VirtualBox Manager (from the start programs in windows search for VirtualBox Manager)
2. Select your Docker Machine VirtualBox image (e.g.: default)
3. Open Settings -> Network -> Advanced -> Port Forwarding
4. Add your app name, the desired host port and your guest port i.e, app name : nginx, host: 127.0.0.1, host port: 80, guest port: 80

Step #04: Now you’re ready to start your Docker Machine by executing the following:

docker-machine start default

Then just start your Docker container and you will be able to access it via localhost.

Have a look here for details.

Answer 5

To map the ports expected to localhost instead of hitting the docker-machine IP directly, you can use the VirtualBox CLI.

If the docker-machine VM (here called default) is running, add and delete rules like this:

> VBoxManage.exe controlvm "default" natpf1 "nginx,tcp,,8888,,8888"
> VBoxManage.exe controlvm "default" natpf1 delete nginx

If the VM is not running, or you want to stop before altering it:

> docker-machine stop
> VBoxManage.exe modifyvm "default" --natpf1 "nginx,tcp,,8888,,8888"
> VBoxManage.exe modifyvm "default" --natpf1 delete "nginx"
> docker-machine start

Where the format of the port forwarding rule is [<name>],tcp|udp,[<hostip>],<hostport>,[<guestip>], <guestport>.

Note that in VirtualBox, you want to map to the host port of Docker map, not the internal container port. You're mapping host -> VM, then Docker maps VM -> container.

See the VirtualBox docs.

Answer 6

This is another easy way to avoid typing the ip 192.168.99.100. Go to C:\Windows\System32\drivers\etc\hosts and add at the end of the file:

192.168.99.100 docker.awesome or any name of your liking.

Save the file (You need to have admin rights so make sure you right click on the file and run as administrator to be able to save it when you edit it).

Go to your chosen domain name, docker.awesome:8080 in this case and there you have it.

Answer 7

After lot of trials, I was able to get this bulletin board.

1. The docker run command I used - docker run -p 4680:8080 --name bb bulletinboard:1.0 Here, 4680 is localhost port number. 8080 is container port number, the port at which the container will be listening. This port number is mentioned in the EXPOSE command in the Dockerfile.

2. Then, go to web-browser and type 192.168.99.100:4680

Here, 192.168.99.100 is the docker machine IP address (use command -> docker-machine ip)

3. After this, your browser page should open to -

Hope this helps you all!!