Basic ASP .NET Core with Docker: Beginners Guide

Cesar Sulbaran
Apr 4, 2019 · 7 min read

Hi Developers ^.^

This is a really short tutorial about how you may set up fast and easily a simple .NET applicaction with Docker

So, things you will get from this post will be:

  1. Having a clearer idea about what is .NET and one approach about how you should start or where you may start
  2. Learning the basics about Docker to deploy your application

Oh right! then let’s start from the beginning, what is .NET and what is Docker?


.NET is a free, cross-platform, open source developer platform for building many different types of applications.

With .NET, you can use multiple languages, editors, and libraries to build for web, mobile, desktop, gaming, and IoT.

What about .NET Core? NET Core is the framework that support ASP.NET, is a cross platform, open source re-implementation of the .NET Framework. If you want to know more in depth, I recommend you this.NET Core.

And ASP .NET? makes easy to create MVC Applications. It provides a languange named razor to build views. Basically, allow to insert C# code inside HTML, reducing coding and increasing the productivity.

You can learn more about .NET on the official page:


Docker is a tool designed to make it easier to create, deploy, and run applications by using containers. Containers allow a developer to package up an application with all of the parts it needs, such as libraries and other dependencies, and ship it all out as one package.

I really like this definition, you can read more about it on: or you may want to go to the official where you can read about containers as well:


In order to moving forward with this tutorial you will need to have some softwares already installed on your pc, on this links you will find an installation step by step guide for Windows / Linux / MAC Platforms:

If you are able to run these commands in your shell, then you are ready to go!

Ok, let’s put hands on the code:

Open a terminal and create some folders:

mkdir NetCore-Docker
cd NetCore-Docker
mkdir src
cd src
mkdir AspMVC
cd AspMVC

Once you have created this folder tree and have your shell on AspMVC folder we create or .Net Core project:

dotnet new MVC

You should get something like this:

Now we open our project with our prefered text editor, and should have a folder tree similar to this:

At this moment we have already the basic files and structure to start creating an ASP .NET application but it isn’t dockerized, let’s do a few more steps before bring docker to the field.

Let’s run this command from command line:

dotnet publish -o ./publish

You should get something like this:


cd publish
dotnet AspMVC.dll

You will get this:

You can also run this command from AspMVC folder:

dotnet run

And will get:

In your browser you will get a basic view like this either running dotnet run or dotnet AspMVC.dll, and if you have troubles with https just add the exception and it should open:

So basically we are running an ASP .NET app directly from our computer, this is what we want to achieve but without using our local dotnet software, instead, we want to use docker.

Dockerizing our app

In order to understand what we want to do, we have to understand this:

  1. Docker images

A Docker image is a file, comprised of multiple layers, used to execute code in a Docker container. An image is essentially built from the instructions for a complete and executable version of an application, which relies on the host OS kernel. When the Docker user runs an image, it becomes one or multiple instances of that container.

2. Docker containers

A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another. A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.

So images is what we build and containers is an instance of that build that runs our code, what we want to do is create sucessfully an image that we can use to run an instance of that image, that means a container that will run our code

Let’s start for creating our Dockerfile, at this moment your shell should be located either NetCore-Docker/src/AspMVC/publish or NetCore-Docker/src/AspMVC, we need to go to our root folder, that would be NetCore-Docker

cd ../../../# Make sure you are in the root directory! ---> NetCore-Docker
# Create new file with the name Dockerfile (extension is not required)
code Dockerfile

Now open a new file (or create) called Dockerfile on my root directory, since i use Visual Studio Code:

On this file we are going to copy this:

I must say this is the way that actually propose microsoft to dockerize an app, you can check it here:

But there is another way, that could result a little bit easier to understand:

If you want to know what means every reserved word and how to use it, please check:

So once we got our file ready we go back to our console. Here we create our image

docker build -t myapp .

You should be getting an input similar to that, once it has finished, we run these commands, this will create an instance of our image, that means, create our container that will run our code and the second command will list us what containers we got running in our computer:

docker run -d -p 8080:80 --name MyNetApp myapp
docker ps

If everything is ok, you should be getting something similar to this:

That means our app is already working and dockerized, and we can check it writing in our browser http://localhost:8080 and we should get the same Home Page, that we got earlier running our app directly from our dotnet installed directly in our pc

Please note that when we run

docker run -d -p 8080:80 --name MyNetApp myapp

It has a few parameters

  • -d: Run container in background and print container ID
  • -p: Especify the port mapping we want to do, left side is our computer port where we want to access to the container, right side is container port that we want to be listeting
  • — name: Name of the container
  • myapp: name of my image, that we just built

When we run

docker ps

We are listing all our running containers.

If you want to list all your images, you can just type console

docker images

And you should see a list with all image that you have on your computer, like this:

That’s it, we did it! Now we can start coding our app and easily deploy it or run it from everywhere where we can run Docker. I strongly suggest you to read about docker compose. It’s a tool that let you run multiples containers and all of them connected between each other :O.

In real world this is really common since we need to run a DB Server, with a FrontEnd Server and a BackEnd Server to run a full application.

You can get the files from:

You will find a file call Dockerfile and Dockerfile1 if you want to switch between how you build your images just rename the file Dockerfile1 to Dockerfile or viceversa and run the same commands

What’s next?

Here are some useful articles to continue learning Docker and .NET Core

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade