Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Docker ip for windows

I'm testing out Docker with a basic .NET core project. I Build and image from this docker file:

FROM microsoft/dotnet:latest

COPY . /app

WORKDIR /app/API

RUN ["dotnet", "restore"]

RUN ["dotnet", "build"]

EXPOSE 5000/tcp

CMD ["dotnet", "run", "--server.urls", "http://*:5000"]

I run it and it goes flawlessly. Now the only problem is, on what IP is it running ?

I'm running Docker on Windows!

Regards

like image 278
TanguyB Avatar asked Jan 18 '17 00:01

TanguyB


People also ask

What is the IP of Docker windows?

Usually Docker uses the default 172.17. 0.0/16 subnet for container networking.

How do I find my Docker IP?

You can easily get the IP address of any container if you have the name or ID of the container. You can get the container names using the "Docker ps -a" command. This will list all the existing containers.

What IP address does Docker use?

By default, Docker uses 172.17. 0.0/16.


2 Answers

You're already exposing the port internally, so the only other thing I can suggest is to check you are opening the port when launching your image too:

docker run -it -p 5000:5000 <imagename>

This will open port 5000 inside the instance to port 5000 on your local machine, and should then be accessible on 127.0.0.1:5000 or localhost:5000.

You should also ensure that you are accepting any host name within Main() in Program.cs with .UseUrls("http://*:5000/") on your WebHostBuilder.

like image 167
Polynomial Avatar answered Oct 15 '22 08:10

Polynomial


I had some issues with running linux containers built for dotnet asp.net core 2 on docker for windows.

The command I was using to run my container was:

docker run -it --rm -p 3394:3394 --name <name> <container>

I could shell to the container and verify the app was listening and returning results.

However, trying to access the app from my machine on port 3394 wouldn't work for 127.0.0.1, localhost, or my machine's NAT ip on the network.

However, running this command gives the IP address allocated by the docker host:

docker inspect -f "{{ .NetworkSettings.IPAddress }}" <name>

In my case the IP was 172.17.0.2. However, accessing 172.17.0.2:3394 still didn't work.

The last piece needed was to run the following in an elevated dos prompt:

route /P add 172.0.0.0 MASK 255.0.0.0 10.0.75.2

This added a route so my machine didn't seek the address via my WAN, which was diagnosed via tracert.

Credit goes to https://github.com/docker/for-win/issues/221

like image 12
user326608 Avatar answered Oct 15 '22 09:10

user326608