Next up, we want to deploy this docker image to k8s. If all worked you should see the Razor demo home page again, but now we’re seeing if within the docker instance. Now check the image is running okay by using curl as we did previously. If you want to check the image works as expect then run the following Here’s the Dockerfile for building an image, it’s basically going to publish a release build of our Razor application then set up the image to run the razordemo.dll via dotnet from a Docker instance.įROM /dotnet/sdk:5.0 AS build Note: If you changed launchSettings.json to use 0.0.0.0, reset this to localhost. Now use your browser to access and you should see the Razor demo home page, or use curl to see if you get valid HTML returned, i.e.

It’d be good to see this is all working, so if let’s run the demo using If you’re running this on a remote machine don’t forget to change launchSettings.json localhost to 0.0.0.0 if you need to.NET core Razor application (mine’s named razordemo), you can do this from Visual Studio or usingĭotnet new webapp -o razordemo -no-https -f net5.0 We’ll create a standard dotnet ASP.NET core Razor application which you can obviously do what you wish to, but we’ll take the default implementation and turn this into a docker image and then deploy it to k8s. Note: Kubernetes is deprecating its support for Docker, however this does not mean we cannot deployed docker images, just that we need to use the docker shim or generated container-d (or other container) images. Let’s look at the steps for deploying our own Docker image to k8s and better still let’s deploy a dotnet core webapp. This post follows on from that one, so do refer back to it if you have any issues with the following configurations etc. In the previous post we looked and an “off the shelf” image of nginx, which we deployed to Kubernetes and were able to access externally using Ingress.

Play framework on docker on kubernetes