Dockerize .NET 6 in 10 Minutes

In this video, we're going to Dockerize our .NET 6 Web API built with TDD. We'll see how to build a multi-stage Dockerfile step-by-step. By containerizing our web API, it'll be much more convenient to manage the deployment our application to a variety of environments on-prem and in the cloud. We'll also set up a health check endpoint!

• 🤝 Become a Patron of the Channel!
Patreon supporters get access to source code from all episodes!

• 👋 Get in Touch!

​​• 🧑🏽‍💻 Udemy Courses

• 🕘 Timestamps
0:00 - Intro
1:23 - Recap of the API
3:07 - Creating a Dockerfile
7:01 - Building the Docker image
8:25 - Running a Docker Container
10:01 - Testing Locally in Browser
10:25 - Adding a Health Check
12:00 - Rebuilding
12:49 - Testing Health Check in Browser

• 📚 Topics Covered in This Video
► Docker
► DevOps
► Dockerfile
► Dockerizing .NET
► .NET Health Check
► Docker multi-stage build
► Docker tagging► .NET 6► Web API Development

[williscoolerthanu]

It is understated how nice it is that you are brief and well spoken. This stuff always ends up being an hour long video for 10 minutes worth of info.

[Gollumfili]

Just found your channel and I wish I had found it sooner! How you only have 40k is beyond me, excellent content that I can't wait get stuck into

[Azm]

Thank you! and of course so glad to see you again!

[axelgrefslie]

Just stumbles upon your channel, and very impressed of the quality of the videos and your teaching skills! Keep up the good work!

[rajeshkannan]

Great Work !!! This is the clean and clear video of containerizing an api I have ever seen. Thanks for the short and superb video.

[MarkDanielLouwe]

I can really say good configs are also an asset. Thank you!

[anuragchauhan]

Thank you Wes Doyle for your I was facing an issue and after watching this video....and follow the steps you mentioned, it worked for me, seamlessly. Thanks once again

[Kricris]

Thank you very much, i'm just days into docker and i'm very invested.
Love to see people that take the effort to explain <3

[ahmedelgendy]

excellent this is the simplest example i see, thank you

[jovemprogramador]

Perfect video, explained in a simple way

[pt_trainer]

Thanks, i struggled with those overriding of ENV variables and wondered why it kept using port 80

[atuldongare]

A really good explanation. Short and simple.

[janivimal]

Great session, simple and easy to understand, Thank you !!

[obadayahya]

Keep Going, thanks for the simple explanation

[michelchaghoury]

very helpfull please keep going we need more and more of your content, especialy more technicaly and more in depth, thank you

[fernandoalanfillmann]

Thank you soo much! Very well explained!

[MrTatPol]

gracias por el tip de correr docker con la variable ASPNETCORE_URLS configurada, no entendía porque siempre se iba a la puerta 80!. Muy agradecido

[jacobphillips]

Great walk through man! Do you mind telling me what JSON Formatter that is in your browser?

[snivesz]

Thanks that was nice. While watching I had a thought, and you don't cover why we would want a 2 stage build process, perhaps because it's obvious, but also perhaps it is worthy of mention. Why wouldn't we publish directly to a runtime container? Because it would have all the artifacts from your machine allowing it to be built. You could have certain drivers, or registered dlls or environment variables that aren't present in test, or prod. The very reason for containerizing (or a close second) is that by sanitizing the build environment it ensures all team members code that gets merged together still builds in a standalone vanilla environment. In a nutshell its good practice for exposing untracked dependencies. Cheers!

[dgroh]

Great tutorial. What about HTTPS? You configured it in your docker run command, but it's not workking even after exposing 5001. Do you know how to get around on this?