1.0.7-runtime-jessie,1.0.7-runtime,1.0-runtime(1.0/runtime/jessie/Dockerfile)1.0.7-runtime-deps-jessie,1.0.7-runtime-deps,1.0-runtime-deps,1-runtime-deps(1.0/runtime-deps/jessie/Dockerfile)1.1.4-runtime-jessie,1.1.4-runtime,1.1-runtime,1-runtime(1.1/runtime/jessie/Dockerfile)1.1.4-sdk-jessie,1.1.4-sdk,1.1-sdk,1-sdk(1.1/sdk/jessie/Dockerfile)2.0.0-runtime-stretch,2.0-runtime-stretch,2.0.0-runtime,2.0-runtime,2-runtime,runtime(2.0/runtime/stretch/amd64/Dockerfile)2.0.0-runtime-jessie,2.0-runtime-jessie,2-runtime-jessie(2.0/runtime/jessie/amd64/Dockerfile)2.0.0-runtime-deps-stretch,2.0-runtime-deps-stretch,2.0.0-runtime-deps,2.0-runtime-deps,2-runtime-deps,runtime-deps(2.0/runtime-deps/stretch/amd64/Dockerfile)2.0.0-runtime-deps-jessie,2.0-runtime-deps-jessie,2-runtime-deps-jessie(2.0/runtime-deps/jessie/amd64/Dockerfile)2.0.0-sdk-2.0.2-stretch,2.0-sdk-stretch,2.0.0-sdk-2.0.2,2.0-sdk,2-sdk,sdk,latest(2.0/sdk/stretch/amd64/Dockerfile)2.0.0-sdk-2.0.2-jessie,2.0-sdk-jessie,2-sdk-jessie(2.0/sdk/jessie/amd64/Dockerfile)
2.0.0-runtime-nanoserver-1709,2.0-runtime-nanoserver-1709(2.0/runtime/nanoserver-1709/amd64/Dockerfile)2.0.0-sdk-2.0.2-nanoserver-1709,2.0-sdk-nanoserver-1709(2.0/sdk/nanoserver-1709/amd64/Dockerfile)
1.0.7-runtime-nanoserver-sac2016,1.0.7-runtime,1.0-runtime(1.0/runtime/nanoserver-sac2016/Dockerfile)1.1.4-runtime-nanoserver-sac2016,1.1.4-runtime,1.1-runtime,1-runtime(1.1/runtime/nanoserver-sac2016/Dockerfile)1.1.4-sdk-nanoserver-sac2016,1.1.4-sdk,1.1-sdk,1-sdk(1.1/sdk/nanoserver-sac2016/Dockerfile)2.0.0-runtime-nanoserver-sac2016,2.0-runtime-nanoserver-sac2016,2.0.0-runtime,2.0-runtime,2-runtime,runtime(2.0/runtime/nanoserver-sac2016/amd64/Dockerfile)2.0.0-sdk-2.0.2-nanoserver-sac2016,2.0-sdk-nanoserver-sac2016,2.0.0-sdk-2.0.2,2.0-sdk,2-sdk,sdk,latest(2.0/sdk/nanoserver-sac2016/amd64/Dockerfile)
2.0.0-runtime-stretch-arm32v7,2.0-runtime-stretch-arm32v7,2.0.0-runtime,2.0-runtime,2-runtime,runtime(2.0/runtime/stretch/arm32v7/Dockerfile)2.0.0-runtime-deps-stretch-arm32v7,2.0-runtime-deps-stretch-arm32v7,2.0.0-runtime-deps,2.0-runtime-deps,2-runtime-deps,runtime-deps(2.0/runtime-deps/stretch/arm32v7/Dockerfile)
Note: The Docker images in this repo are supported by Microsoft. The
arm32v7images are in preview and have "best effort" support only by the community and .NET Core Team. Please see the arm32 announcement for more details.
Note: Watch dotnet/announcements for Docker-related .NET Core announcements.
For more information about these images and their history, please see the relevant Dockerfile (dotnet/dotnet-docker). These images are updated via pull requests to the dotnet/dotnet-docker GitHub repo.
.NET Core is a general purpose development platform maintained by Microsoft and the .NET community on GitHub. It is cross-platform, supporting Windows, macOS and Linux, and can be used in device, cloud, and embedded/IoT scenarios.
.NET has several capabilities that make development easier, including automatic memory management, (runtime) generic types, reflection, asynchrony, concurrency, and native interop. Millions of developers take advantage of these capabilities to efficiently build high-quality applications.
You can use C# to write .NET Core apps. C# is simple, powerful, type-safe, and object-oriented while retaining the expressiveness and elegance of C-style languages. Anyone familiar with C and similar languages will find it straightforward to write in C#.
.NET Core is open source (MIT and Apache 2 licenses) and was contributed to the .NET Foundation by Microsoft in 2014. It can be freely adopted by individuals and companies, including for personal, academic or commercial purposes. Multiple companies use .NET Core as part of apps, tools, new platforms and hosting services.
You can run a sample application (Linux image) that depends on these images in a container by running the following command.
docker run microsoft/dotnet-samples.NET Core Docker images can use multi-stage build. This feature allows multiple FROM instructions to be used in one Dockerfile. Using this feature, you can build a .NET Core app using an SDK image (AKA 'build image') and then copy the published app into a lighter weight runtime image within a single Dockerfile.
You can check out our multi-stage build samples on GitHub for ASP.NET apps, production scenarios, and self-contained scenarios.
Add a Dockerfile to your .NET project with the following:
FROM microsoft/dotnet:sdk AS build-env
WORKDIR /app
# copy csproj and restore as distinct layers
COPY *.csproj ./
RUN dotnet restore
# copy everything else and build
COPY . ./
RUN dotnet publish -c Release -o out
# build runtime image
FROM microsoft/dotnet:runtime
WORKDIR /app
COPY --from=build-env /app/out ./
ENTRYPOINT ["dotnet", "dotnetapp.dll"]Build and run the Docker image:
docker build -t dotnetapp .
docker run --rm dotnetapp Hello .NET Core from DockerThe Dockerfile and the Docker commands assumes that your application is called dotnetapp. You can change the Dockerfile and the commands, as needed.
You can use the .NET Core SDK Docker image as a build and runtime environment. It's a useful image for iterative development and the easiest way to get started using .NET Core with Docker. It isn't recommended for production since it's a bigger image than necessary, although it can work for that, too. You can try the instructions below or use the dotnetapp-dev sample if you want to try a pre-made version that's ready go.
Create a Dockerfile with following lines, which will both build and run your application in the container. This Dockerfile has been optimized (note the two COPY commands) to take advantage of Docker layering, resulting in faster image building for iterative development.
FROM microsoft/dotnet
WORKDIR /dotnetapp
# copy project.json and restore as distinct layers
COPY project.json .
RUN dotnet restore
# copy and build everything else
COPY . .
RUN dotnet publish -c Release -o out
ENTRYPOINT ["dotnet", "out/dotnetapp.dll"]You can then build and run the Docker image:
docker build -t dotnetapp .
docker run -it --rm dotnetappThe Dockerfile and the Docker commands assumes that your application is called dotnetapp. You can change the Dockerfile and the commands, as needed.
You can interactively try out .NET Core by taking advantage of the convenience of a container. Try the following set of commands to create and run a .NET Core application in a minute (depending on your internet speed).
docker run -it --rm microsoft/dotnet
[now in the container]
mkdir app
cd app
dotnet new console
ls
dotnet restore
dotnet run
dotnet bin/Debug/netcoreapp1.0/app.dll
dotnet publish -c Release -o out
dotnet out/app.dll
exitThe experience is very similar using Windows Containers. The commands should be the same, with the exception ls and the directory separators.
The steps above are intended to show the basic functions of .NET Core tools. Try running dotnet run twice. You'll see that the second invocation skips compilation. The subsequent command after dotnet run demonstrates that you can run an application directly out of the bin folder, without the additional build logic that dotnet run adds. The last two commands demonstrate the publishing scenario, which prepares an app to be deployed on the same or other machine, with a requirement on only the .NET Core Runtime, not the larger SDK. Naturally, you don't have to exit immediately, but can continue to try out the product as long as you want.
You can extend your interactive exploration of .NET Core by git cloning the dotnet/dotnet-docker-samples repo. Try the following commands (only works on Linux containers), assuming you are running interactively in the container:
git clone https://github.com/dotnet/dotnet-docker-samples
cd dotnet-docker-samples
cd dotnetapp-dev
dotnet restore
dotnet runYou can interactively try out ASP.NET Core by taking advantage of the convenience of a container. Try the following set of commands to create and run an ASP.NET Core application in a minute (depending on your internet speed).
docker run -p 8000:80 -e "ASPNETCORE_URLS=http://+:80" -it --rm microsoft/dotnet
[now in the container]
mkdir app
cd app
dotnet new mvc
dotnet restore
dotnet run
exitAfter running dotnet run in the container, browse to http://localhost:8000 in your host machine.
The experience is very similar using Windows Containers. The commands should be the same, with the exception of the docker run. Replace the docker run command above with the following two commands:
docker run -e "ASPNETCORE_URLS=http://+:80" -it --rm microsoft/dotnet
ipconfigCopy the IP address from the output of ipconfig. After running dotnet run in the container, browse to that IP address in your browser on your host machine.
You should see a default ASP.NET Core site and logging activity in the container.
Please use the images at microsoft/aspnetcore. They are recommended and optimized for ASP.NET core development and production and are built on the images in this repo.
The microsoft/dotnet images come in different flavors, each designed for a specific use case.
See Building Docker Images for .NET Core Applications to learn more about the various Docker images and when to use each for them.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
It contains the .NET Core SDK which is comprised of two parts:
- .NET Core
- .NET Core command line tools
Use this image for your development process (developing, building and testing applications).
This image contains the .NET Core (runtime and libraries) and is optimized for running .NET Core apps in production.
This image contains the operating system with all of the native dependencies needed by .NET Core. This is for self-contained applications.
You can learn more about using .NET Core with Docker with .NET Docker samples:
- .NET Core Development Sample - This sample is good for development and building since it relies on the .NET Core SDK image. It performs
dotnetcommands on your behalf, reducing the time it takes to create Docker images (assuming you make changes and then test them in a container, iteratively). - .NET Core Docker Production Sample - This sample is good for production since it relies on the .NET Core Runtime image, not the larger .NET Core SDK image. Most apps only need the runtime, reducing the size of your application image.
- .NET Core self-contained application Docker Production Samp - This sample is also good for production scenarios since it relies on an operating system image (without .NET Core). Self-contained .NET Core apps include .NET Core as part of the app and not as a centrally installed component in a base image.
- ASP.NET Core Docker Production Sample - This samples demonstrates a Dockerized ASP.NET Core Web App.
See the following related repos for other application types:
- microsoft/aspnetcore for ASP.NET Core images.
- microsoft/aspnet for ASP.NET Web Forms and MVC images.
- microsoft/dotnet-framework for .NET Framework images (for web applications, see microsoft/aspnet).
- microsoft/dotnet-nightly for pre-release .NET Core images (used to experiment with the latest builds).
View license information for the software contained in this image.
The .NET Core Windows container images use the same license as the Windows Server 2016 Nano Server base image, as follows:
MICROSOFT SOFTWARE SUPPLEMENTAL LICENSE TERMS
CONTAINER OS IMAGE
Microsoft Corporation (or based on where you live, one of its affiliates) (referenced as “us,” “we,” or “Microsoft”) licenses this Container OS Image supplement to you (“Supplement”). You are licensed to use this Supplement in conjunction with the underlying host operating system software (“Host Software”) solely to assist running the containers feature in the Host Software. The Host Software license terms apply to your use of the Supplement. You may not use it if you do not have a license for the Host Software. You may use this Supplement with each validly licensed copy of the Host Software.
Supported Docker versions: the latest release (down to 1.12.2 on a best-effort basis)
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, please read the .NET Core contribution guidelines.
You can read documentation for .NET Core, including Docker usage in the .NET Core docs. The docs are open source on GitHub. Contributions are welcome!