Docker Docker.For..Localhost Mac Book Pro

Strong believer of developer community, passionate about Software development and Architecture.

The two main parts of the solution are the MVC core application which acts as front end and there is a ASP.Net Core Web API which provides some static key value pairs.

Docker Docker.For..Localhost Mac Book Pro

Problem communicating between MVC App Web API I am using Mac Book Pro 2016 model to develop and test this application.

The web application and the Api both were running successfully when they are run using the dotnet run command.

Within the web application there is a provision to provide the url for the webapi and the search can be made dynamically referring to a valid instance of running web api.

Next we see the MVC app working by referencing the webapi Once my test were successful locally, I moved on to containerize the MVC app and web Api as Docker images.

Running the two images individually also worked fine using the commands shown below docker run d p 80:80 coremvc docker run d p 8080:80 corewebapi The last step before I publish the images to Docker registry like Dockerhub was to test the web api by invoking a method from within a container image.

As seen from the above command, I am mapping the 8080 command on docker host which is my Mac to the web api container port on 80.

If I use, I should get a result similar to what is shown above.

I tried to access the API keyValue controller by directly hitting the browser and bypassing the call through web application and it is giving me the correct response.

Why is that the MVC application running inside the container not able to connect to it Docker Networking for Mac The reason for this is to do with the way Docker for Mac handles networking.

When we say localhost, the container tries to connect to services within the container image.

We need a way to route the call through the host and redirect the traffic via host port 8080.

It turns out that there is a special way of accessing localhost while running docker for mac.

As an alternative, we can also use ip address which is 192.168.65.1.

Replacing docker.for.mac.localhost with the this ip gives the same result.

Conclusion Docker is a wonderful technology to develop and test things quickly.

I hope this post was helpful if you are working with multi container applications using ASP.Net Core and Docker.

This problem of accessing other containers using localhost happens only while testing locally.

When I provided the fully qualified API url after deploying the containers to Docker Swarm on Azure Container Service, I di not face the issue.

I will post similar tips and tricks related to Docker and Azure which I am currently exploring.

Always believes that knowledge is grown by sharing with community.

An avid cricket fan who also likes listening to Hindi music.

Please try again and let me know if you are facing issues with the new RSS feed link from the site.

Delete Replies Reply Reply Daria 25 April, 2019 00:29 That saved my day Thanks:) Reply Delete Replies Reply Add comment Load more.

Docker For Mac Docker.For.Mac.Localhost