Creating a Containerized .NET Application

Containers are a tool that allows you to execute your applications inside of a lightweight, isolated environment built on top of a shared kernel. This allows you to create reproducible environments that can be relocated and redeployed quickly with similar results meaning that a container can be built once and then run on your local machine or in the cloud. This session is intended to introduce some of the concepts behind containers and how you can interact with them. We'll also be building our own local container using Docker that is able to run a .NET application for us. You will learn what a container is, some of the common use cases and the steps you need to take to build, run and interact with your containers.

A container image is a blueprint that represents the filesystem structure and configuration needed to create a container. These images are typically built in a series of layers describing the other images it is based on or the steps required to create the initial image. These steps might COPY files from your local filesystem into the image, RUN code or scripts or a number of other tasks.

Containers themselves are instances of the containers image. Multiple containers of the same image can be created and run simultaneously, in environments that are isolated from one another. Each container instance will have its own filesystem, memory and network interface that can be configured uniquely for that container.

We'll be creating a quick .NET application in C# and then building a Dockerfile that describes the image we will be creating. Using that image we'll build and run a container that executes our app. The code we'll write will be able to be run on your own machine but will require .NET and Docker.

Speaker:
Sam Wronski, Cloud Advocate, Microsoft

[eventID:14312]