Ms visual studio publish to lightsail how to#

This time it goes further as the container starts, crashes and restarts. Trying with the above config results in another error: Linux needs to have a user identifier (not name) as an input. Never mind, just specify a user and it should work, right? Let's try:īy the way, if you wonder, when no user is specified in the Docker image itself or through a securit圜ontext, user 0 is assumed and 0 stands for root. But, because you explicitely added a runAsNonRoot instruction, it can't start it. What K8s tells you is that the image wants to start as root because no other user has been defined, so it defaults to root. Warning Failed 94s (x8 over 2m53s) kubelet, aks-agentpool-38789445-vmss000001 Error: container has runAsNonRoot and image will run as root If you don't, by requesting it specifically in your deployment through a securit圜ontext:ĭescribing the pod with Kubectl quickly shows that the container tried to start as root: If you build an image and run this, you must run it as root. RUN dotnet publish 'simpleapi.csproj' -c Release -o /app/publish RUN dotnet build 'simpleapi.csproj' -c Release -o /app/build RUN dotnet restore 'simpleapi/simpleapi.csproj' That said, if you take the simplest ASP.NET web API project and choose the default Visual Studio 2019 template, you'll end up with the following Dockerfile:įROM /dotnet/core/aspnet:3.1-buster-slim AS baseįROM /dotnet/core/sdk:3.1-buster AS buildĬOPY You'll rather stumble upon GitHub issues and questions here and there.Īs you know, ASP.NET relies on the built-in Kestrel web server and most ASP.NET applications are either MVC, either Web APIs, meaning that they are unlikely going to leverage operating system level capabilities that require high privileges.

Ms visual studio publish to lightsail how to#

At the time of writing, I challenge you to find a single source of truth (feel free to add it in comment if I missed any), endorsed by Microsoft on how to to harden an ASP.NET Docker image. Admitedly, there is a lack of guidance from Microsoft in that matter. Basically, most deployments are not hardened properly, and I see countless ASP.NET containers running as root. NET 5) K8s deployments are too permissive when it comes to the execution context. In my day to day job, I often stumbled upon a surprising fact: many ASP.NET Core (or.