This stage actually builds your application. NET SDK, as well as various other dependencies. This stage defines the docker image that will be used to build your application. It contains the minimal dependencies to run your application. This stage defines the base image that will be used to run your application. This Dockerfile uses the best practice of multi-staged builds to ensure your runtime images are as small as possible. WORKDIR '/src/.' RUN dotnet build 'WebApplication1.csproj' -c Release -o /app/build FROM build AS publish RUN dotnet publish 'WebApplication1.csproj' -c Release -o /app/publish FROM base AS final WORKDIR /app COPY -from = publish /app/publish. This generates a Debian-based dockerfile by default (the /dotnet/aspnetcore:6.0 images are Debian based unless you select different tags), which looks like this: FROM /dotnet/aspnet:6.0 AS base WORKDIR /app EXPOSE 80 FROM /dotnet/sdk:6.0 AS build WORKDIR /src COPY RUN dotnet restore './WebApplication1.csproj' COPY. I chose ASP.NET Core Web API, used minimal APIs, disabled https, enabled Docker support (Linux) and generated the solution: I could have used the CLI to create the app, but I decided to use Visual Studio as I knew it would give me the option to auto-generate the Dockerfile as well. I started by creating a sample web application using Visual Studio. Creating the sample app with a Dockerfile. This left me with one obvious answer - build my own CentOS Docker image, and install ASP.NET Core in it 'manually'. Currently, they provide Linux Docker images based on:Īdditionally, while you can install CentOS in WSL, it's a lot more hassle than something like Ubuntu, which you can install directly from the Microsoft Store. Unfortunately, while ASP.NET Core supports CentOS, they don't provide Docker images with it preinstalled. In order to diagnose the issue, I needed to run an ASP.NET Core application on CentOS. I ran into my problem the other day while responding to an issue report related to CentOS.

Background: testing ASP.NET Core on CentOS

In this post I describe a problem I ran into the other day that had me stumped briefly-why doesn't my ASP.NET Core app running in Docker respond when I try and navigate to it? The problem was related to how ASP.NET Core binds to ports by default.

Asp.net core docker on mac