Hosting ASP.NET Core 2.0 Application In Docker

Ravi Raghav

22 Comments

Join the conversation! Your thoughts help the community grow.

Joginder Banger6y ago
Hi bro, I want the deploy docker image on windows server. can you tell me what is the procedure. thanks joginder
Amit Kumar Pal7y ago
Hi Ravi, thanks for sharing, good explained...
Vishal Kadam7y ago
HI Ravi, Thank you for this article.
Vishal Dobariya8y ago
Hi Ravi, When we say that application is running on Docker container in your example, Where exactly it is running? On your local windows box or somewhere on the internet cloud? Looking at IP address, it seems it's not the local box IP.
- Ravi Raghav8y ago
  Hi Vishal, please note that first point is installing docker on my machine. So in this example, this IP is only accessible to me on my computer, not on the internet. If you want to do that then you have to install docker on the server and then you have to expose the docker's port to the internet, that is a very vast and different topic altogether that is why I didn't mention that here. If you want to see how it works you can simply look at Azure fabric and there are many more examples out there.
Farhan Ahmed8y ago
Like it nice one
- Ravi Raghav8y ago
  Thank you!
Faisal Pathan8y ago
Thank you for sharing
- Ravi Raghav8y ago
  Thank you for the appreciation.
Viknaraj Manogararajah8y ago
Nice Article, Thank you for sharing.........
- Ravi Raghav8y ago
  Thank you for the appreciation.
Hadshana Kamalanathan8y ago
Thanks for sharing
- Ravi Raghav8y ago
  Thank you for the appreciation.
Avinash Jorige8y ago
Hi Ravi, this article is good and helped me a lot, thanks.
- Ravi Raghav8y ago
  Thank you for the appreciation.
Ravishankar N8y ago
Nice article. Thanks fot sharing
- Ravi Raghav8y ago
  Thank you for the appreciation.
Ashish Christian8y ago
Hi Ravi, Thanks for this article. I have run docker-compose build this command but I got an error *ERROR: Service 'test01' failed to build: error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/5f/5fef67803e08bc5f4f5aadc73ccc099e05feda1f4aad6ee2ece423bc3a332b61/data?verify=1531481150-P5kdGsjQSpFsfK8d6B8c10mSMfg%3D: dial tcp 104.18.125.25:443: i/o timeout* Here test01 is my project name.
- Ashish Christian8y ago
  Thanks for your reply, I am using docker in windows. I have follow all step to install docker in windows.Please check the below details of my decker version.Client: Version: 18.03.1-ce API version: 1.37 Go version: go1.9.5 Git commit: 9ee9f40 Built: Thu Apr 26 07:12:48 2018 OS/Arch: windows/amd64 Experimental: false Orchestrator: swarm Server: Engine: Version: 18.03.1-ce API version: 1.37 (minimum version 1.12) Go version: go1.9.5 Git commit: 9ee9f40 Built: Thu Apr 26 07:22:38 2018 OS/Arch: linux/amd64 Experimental: false Still I am getting the this type of issue. Even not in above command, I just enter command for pull the "hello-world" request this pull request is also fail and throw the timeout error.
- Christian Ashish8y ago
  Hi Ashish, That same problem generated from my side. If you find the solution then Please share with me dear. I am stuck with that error.
- Ravi Raghav8y ago
  Hi Ashish, There are many possible reasons for this, you might be deploying on windows but you may have Linux dockers enable, if you do not have admin access then you might need to run docker login command for more information you can check out this link https://github.com/docker/compose/issues/4807 and if none of it works if you are working on windows then just restart your command prompt and run the same command again, make sure you are in the project directory in command prompt before running build command

In today's article, we will create an ASP.NET Core 2.0 MVC web application with Docker support and then, we will deploy our application in a Docker container (Windows 10).

Why do we need this?

The main purpose of Docker is to deploy applications to the production environment or other environments as required by Ops. However, the highlight of Docker lies in the process of deploying it.

Till Docker came into the picture, the traditional approach to deployment was via Virtual Machines (VM). And let’s not get started with the drawbacks of VMs because there are a plenty. Starting from the effort required to boot a VM, to launching multiple VMs in the same machine, it is a tough task to get things running with VMs.

So first, let’s see what does Docker provide?

Docker provides a container environment which can be used to host any application of your choice. The software application and the dependencies which support it are tightly-packaged together.

This packaged product is called a Container. Since it is done by Docker, it is called a Docker container!

Benefits of Docker container?

Since the application and its dependencies are packaged together, there is no external dependency for the app to run. This means the container is very light-weight.

Because it is light-weight, it can be easily shipped to other machines and be executed on those machines, irrespective of their host OS/ configurations.

The only requirement being, Docker has to be installed to run that application residing in the container.

So let's get started.

We will install docker for windows (we are using windows 10).

For that go to the following link - https://store.docker.com/editions/community/docker-ce-desktop-windows

You will need to login in order to download this. Once you have downloaded the setup and installed then restart your system.

After restarting go to command prompt and type docker version

You should see something like this in your console.

It means that docker is successfully installed in your machine. Now we will create our ASP.NET Core 2.0 MVC application.

Make sure to check Enable Docker Support checkbox and select your OS (mine is windows)

Once the project is created then you will see some docker files in the solution explorer,

When we open Dockerfile,

These are the contents of the auto-generated file.

What this file does is defines the dependencies which are required for our application and when we host our application in docker then this file is read by the docker to get the dependencies and get the entry point for our application.

So our application part is done. Now we will simply host our application in the docker container.

For that open command prompt and go to the project location where DockerFile resides and type docker-compose build and hit enter.

You will see some processes, let them execute

After all the steps are done you should see something like this,

After this to see the images type docker images and hit enter,

You should see your application like this. So this is our image. But the image is just a template, we cannot connect to it, to run it we have to put this image inside a container and the run that container. So for that, we will copy its image id and type docker run your_image_id,

As you can see now our application is running. So to open it in our browser we need IP address of our container which has the image. To check that type docker ps –a and hit enter,

Here we can see our container that is just been created and now to get the IP address of our container type docker inspect your_container_id

It will give you information about your container like this

ASP.NET Core

You will get all of this information, now scroll down and look for NetworkSettings

ASP.NET Core

You will need this highlighted IP address.

There is another way to get this IP Address and that is to type the following

docker inspect -f "{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}" your_container_id

So now that we have got the IP address just enter this address in the browser.

And here you can see our application running on a docker container.

Summary

In this article, we have seen how to deploy our ASP.NET Core 2.0 MVC web application into a docker container and run it through the IP address of the container rather than the localhost.

I hope you all liked it.