Shulou(Shulou.com)06/02 Report--

This article focuses on "how to run ASP.NET Core in the Docker container of Linux and Windows". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to run ASP.NET Core in the Docker container of Linux and Windows.

I installed the following things:

Visual Studio Community 2015

Visual Studio 2015 Update 3

ASP.NET Core with .NET Core

.net Core 1.0.1-VS 2015 Tooling Preview 2

Docker for Windows (I use the Beta channel)

Visual Studio Tools for Docker

Docker for Windows is really good, it can automatically configure Hyper-V for you, create a Docker host OS, and start the virtual machine. Saved a lot of time.

This is my Linux host, and I don't need to care much about it. I will do everything through the command line or Visual Studio.

First, use File | New Project to create an ASP.NET Core application running in the .NET Core.

Then right-click on the project name and select Add | Docker Support. This menu comes from the Visual Studio Tools for Docker extension. This step adds basic Dockerfile and other docker-compose files. With such out-of-the-box steps, I have done all the configuration so that I can deploy the ASP.NET Core application to the Docker Linux container.

ASP.NET Core runs in a Docker Linux container

From my ASP.NET Core application, we can see that the basic image it uses (that is, the FROM statement in Dockerfile) is the ASP.NET Core image of Linux.

FROM microsoft/aspnetcore:1.0.1

ENTRYPOINT ["dotnet", "WebApplication4.dll"]

ARG source=.

WORKDIR / app

EXPOSE 80

COPY $source.

Next, since I don't want Docker to compile my application, I just want to publish it locally. You can read Steve Laske's blog article "Building Optimized Docker Images with ASP.NET Core" to learn how to build an application in one container and run it in another. This optimizes server utilization and resources.

I will publish, build the image, and run it with the following command line instructions.

> dotnet publish

> docker build bin\ Debug\ netcoreapp1.0\ publish-t aspnetcoreonlinux

> docker images

REPOSITORY TAG IMAGE ID CREATED SIZE

Aspnetcoreonlinux latest dab2bff7e4a6 28 seconds ago 276.2 MB

Microsoft/aspnetcore 1.0.1 2e781d03cb22 44 hours ago 266.7 MB

> docker run-it-d-p 85:80 aspnetcoreonlinux

1cfcc8e8e7d4e6257995f8b64505ce25ae80e05fe1962d4312b2e2fe33420413

> docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

1cfcc8e8e7d4 aspnetcoreonlinux "dotnet WebApplicatio" 2 seconds ago Up 1 seconds 0.0.0.0 seconds ago Up 85-> 80/tcp clever_archimedes

At this point, my ASP.NET Core application can run in Docker. We have now tried a Docker container, which is hosted in a Linux host that runs through Hyper-V in Windows.

What else can we do?

ASP.NET Core runs in a Docker Windows container running Windows Nano Server

There is one kind of Windows Server, called Windows Server Core, which removes things related to UI, and there is a kind of Windows Server, called Windows Nano Server, which reduces Windows to only a few hundred megabytes instead of a few gigabytes. This means that from the perspective of required functionality and server usage, this is a very good choice to make your deployment space as small as possible.

Let me see if I can run ASP.NET Core into Windows Nano Server via Kestrel. Of course, because of the power of Nano, I can also run IIS in this container, as documented here.

Michael Friis from Docker has a great blog post about building and running Docker applications in a Windows Server container. After installing the latest version of Docker for Windows, you can switch between Linux and Windows containers through the context menu.

So now I'm going to use Docker with a Windows container. You may not know that you already have a Windows container! It has been released with the 10th anniversary update of Windows. You can enable the container function in the Windows Properties dialog box:

I'm going to modify the Dockerfile to use the Windows Nano Server image. I can also control the ports exposed by ASP.NET through environment variables and Expose commands within Docker.

FROM microsoft/dotnet:nanoserver

ENTRYPOINT ["dotnet", "WebApplication4.dll"]

ARG source=.

WORKDIR / app

ENV ASPNETCORE_URLS http://+:82

EXPOSE 82

COPY $source.

Then, I release and build...

> dotnet publish

> docker build bin\ Debug\ netcoreapp1.0\ publish-t aspnetcoreonnano

Then, run it and map the Windows external port to the inside of the Windows container!

Note: when Windows 10 communicates with the container through "NAT" (Network address Translation), there is a Bug that you can't access the container application directly through http://localhost:82 as you (I) want. You have to access it through the container's own IP. As soon as I hear more about this Bug and how it has been fixed, I will announce it here in time. It should appear in a few days via Windows Update. The method to obtain the IP address of the container from Docker is: docker inspect-f "{{.NetworkSettings.Networks.nat.IPAddress}}" HASH

So, I will run my ASP.NET Core application in Windows Nano Server with the following command (again, it will run in the Nano Server container of Windows 10).

> docker run-it-d-p 88:82 aspnetcoreonnano

Afafdbead8b04205841a81d974545f033dcc9ba7f761ff7e6cc0ec8f3ecce215

> docker inspect-f "{{.NetworkSettings.Networks.nat.IPAddress}}" afa

172.16.240.197

Now, I can access this site at 172.16.240.197VRO 82. Once the above Bug has been fixed, we can access it like other containers.

The best thing about Windows containers is that they are very fast and lightweight. Once the images are downloaded and built on the machine, it takes a second for you to start and stop them through Docker.

However, you can also use Docker to isolate the Windows container with the following command:

Docker run-- isolation=hyperv-it-d-p 86:82 aspnetcoreonnano

In this way, the instance is run entirely in isolation through the Hyper-v itself. You can get the best things in the world: speed, easy deployment, and optional and convenient isolation.

ASP.NET Core runs in a Docker Windows container running Windows Server Core

Next, I modified the Dockerfile to use a full Windows Server Core image. After downloading and installing the image, it takes up about 8 gigabytes of space and takes a little time to download and extract, but it is a real Windows. You can also choose to run as a container or an isolated Hyper-V container.

Here, I use the Windows Sever Core that contains. NET Core by modifying the FROM statement:

FROM microsoft/dotnet:1.0.0-preview2-windowsservercore-sdk

ENTRYPOINT ["dotnet", "WebApplication4.dll"]

ARG source=.

WORKDIR / app

ENV ASPNETCORE_URLS http://+:82

EXPOSE 82

COPY $source.

Note: I heard that the .NET Core image using Windows Sever Core may be canceled. Because it makes more sense to have the .NET Core run in Windows Nano Server or other lightweight images. You should use Sever Core for more cumbersome applications. If you really need to run .NET Core on Sever Core, you can make your own Dockerfile to easily build the image you want.

Next, I will release, build, and run again.

> docker images

REPOSITORY TAG IMAGE ID CREATED SIZE

Aspnetcoreonnano latest 7e02d6800acf 24 minutes ago 1.113 GB

Aspnetcoreonservercore latest a11d9a9ba0c2 28 minutes ago 7.751 GB

Because the container can start and stop very quickly, I can run a complete Web cluster using Redis running in the container, a SQL container, and a third container that contains other parts. Or mix and pair.

> docker ps

CONTAINER ID IMAGE COMMAND PORTS NAMES

D32a981ceabb aspnetcoreonwindows "dotnet WebApplicatio" 0.0.0.0pur87-> 82/tcp compassionate_blackwell

A179a48ca9f6 aspnetcoreonnano "dotnet WebApplicatio" 0.0.0.0 82/tcp determined_stallman 86->

170a8afa1b8b aspnetcoreonnano "dotnet WebApplicatio" 0.0.0.0 82/tcp agitated_northcutt 89->

Afafdbead8b0 aspnetcoreonnano "dotnet WebApplicatio" 0.0.0.0Suzhou 88-> 82/tcp naughty_ramanujan

Summary of 2cf45ea2f008 a7fa77b6f1d4 "dotnet WebApplicatio" 0.0.0.0 82/tcp sleepy_hodgkin 97->

Third, let's read another article by Michae, who uses Docker Compose to run the ASP.NET Music Store example in one Windows container, while SQL Express runs in another, and Steve Lasker's blog post (in fact, his entire article is a gold mine) to create an optimized Docker image for ASP.NET Core.

IMAGE ID RESPOSITORY TAG SIZE

0ec4274c5571 web optimized 276.2 MB

F9f196304c95 web single 583.8 MB

F450043e0a44 microsoft/aspnetcore 1.0.1 266.7 MB

706045865622 microsoft/aspnetcore-build 1.0.1 896.6 MB

Steve mentions a number of techniques that allow you to solve most of the problems that Docker and ASP.NET Core have together.

All of which means (IMHO) that you can use ASP.NET Core to:

Run ASP.NET Core in Linux

In the Docker container.

In any cloud platform

Run ASP.NET Core in Windows, Windows Server, Server Core and Nano Server

In Docker's Windows container.

In Docker's Hyper-V isolation container.

This means that you can choose sizes that are supported by any feature and optimized for server usage and convenience. Once all the tools (Docker for Windows and Visual Studio Docker Tools) are ready, we can have a good debugging environment and workflow support from development to production.

At this point, I believe you have a better understanding of "how to run ASP.NET Core in the Docker container of Linux and Windows". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.