Nano Server x Server Core x Server - Which base image is the right one for you?

Published Oct 12 2021 03:31 PM 1,306 Views

Almost every week I'm faced with this question from customers: Which Windows base container image is the right one for me? For that reason, I decided to write this blog post to help customers understand the differences between the three Windows container base images, its use cases, and pros and cons from each one.

 

Before we get started, it's important to note that in many cases, there is a framework image that leverages these images above. The most common examples are .Net Framework, ASP. Net, .Net (formerly .Net Core), among many others.

 

What are the base container images

Base images are used (as the name suggests) as basis for the framework and application you want to host. They dictate which OS APIs are available for your application and it could be a large or a small set of APIs. The more APIs are available, the more binaries are needed, resulting in a larger base image. For that reason, when we started to produce these base images we had Server Core and Nano Server, with the Server image being added later to address scenarios not supported by the former images.

LTSC2022 Images.png

 

Nano Server base container image

This is our smallest base container image. As mentioned above, this means less APIs available. For Nano Server, we focused on scenarios where developers will be writing new applications on which the framework can target the specific APIs of Nano Server. Examples of frameworks, languages, or apps that are supported on Nano Server are .Net Core (now called .Net), Apache, NodeJS, Phyton, Tomcat, Java runtime, JBoss, Redis, among others.

Once pulled and extracted, the Nano Server base image has around 290MB in size. That means its pull time is extremely fast, allowing for faster scale-up processes. The other side of this is the already mentioned requirement that only specific frameworks will be supported in this base image.

To provide some history, the Nano Server is actually based on a previously available Nano Server installation option. We discontinued this option a few years ago specifically to focus on the Nano Server base container image. Overall, the general question I recommend customers to ask when developing new applications is to always check if the Nano Server provides the necessary APIs for that application. If so, choose this image as the benefits of a smaller image are great.

 

Server Core base container image

In this case, the scenario expected is different than the Nano Server base image. The Server Core base container image is based on the Server Core installation. This image is focused on lift and shift scenarios, on which the expectation is to get the same application that was working on a VM and put it in a container - as is/no code changes. Of course there's a bunch of limitations here. For example, if the application did not work on Server Core already, it most likely won't work on the Server Core base container image.

More importantly, the Server Core base image supports .Net Framework, which is the framework used on most of the existing (not to say, legacy) applications out there. We see a lot of customers using this image to containerize applications from the Windows Server 2008 era. Not surprisingly, web applications written in ASP.Net 3.5. 

The Server Core image has around 4.8GB after pulled and extracted, which means longer pull times, adding up to the total time of scale-up operations. However, the larger API area should be your target here. Just like on the Nano Server, I have some guidance on this image I provide to customers: First, check if the application you're trying to containerize works on regular Server Core deployments. If not, containers might not be an option here. If it does, you should still make sure you try out the application on a Server Core container to check if the app is not trying to use something from the OS that was removed when building the base container image.

 

Server base container image

This is our largest image, by a lot - but for all the good reasons. This image is based on the "Server with Desktop Experience" installation mode. Of course, the GUI is not present, but the UI APIs are there. This image enables a whole new set of scenarios, including support to GPU via DirectX. 

GPU_Server2022.png

Another interesting scenario enabled by this image is UI automation tests for developers. As mentioned before, you don't get a GUI with this image - rather, the UI APIs are present for UI automation tests to work. Also, some UI automation tools might not be supported on Windows containers at all. If you are familiar with such tools and you know one that doesn't work with Windows containers, please let us know as we're interested in these scenarios.

Of course, the compromise on the Server image is the total size of around 11.2GB, once its layers are downloaded and extracted. On the other hand, think of this base image as your an alternative to containerize an existing app that is not supported on Server Core. The question I ask customers here is: Does the app works on Server Core? If not, try the Server image as that should probably work. See that we start by giving the Server Core a try, as the size would be a great benefit. If it doesn't, the Server image should do the work.

 

Why not say the exact size of these images?

It's easy to fall on the temptation of comparing image sizes for comparison sake. However, just like on regular servers, you should not simply install your system and let it go. Containers are subject to Patch Tuesday and in fact, Microsoft updates these base images every month with security updates. That means you should be updating your production systems composed by containers every month to leverage these security updates. The way you perform that is a topic for another blog post, but the point here is that given these monthly changes, the size of the base container images will vary. Some months we gain some, some months we lose some. The fact that these images have around 290MB (Nano Server), 4.8GB (Server Core), and 11.2GB (Server) should give you a ballpark on what to expect in terms of size. Furthermore, these image layers are compacted for pulling operations (download) so the size that does over the wire is smaller than what you see on disk.

 

Summary

  Nano Server Server Core Server
Size (uncompressed on disk) ~290MB 4.8GB 11.2GB
Based on (installation mode) Nano Server Server Core Server with Desktop
Scenarios New applications being developed for Nano Server Lift and Shift, web applications Lift and Shift, GPU dependent apps, UI automation
Examples .Net (formerly .Net Core) .Net Framework, ASP.Net Framework .Net Framework, DirectX, ML based applications

 

As always, let us know if you have questions or comments, either in the comments section below or in our GitHub repo.

 

Vinicius

Twitter: @vrapolinario

 

Edit:

Some of you might have noticed I left the already known "Windows" image out of the article. That was on purpose, but I wanted to comment on that image so it doesn't create any confusion for current customers. Currently, Microsoft has 4 main base images for Windows containers, the already covered Nano Server, Server Core, and Server. The last one is the Windows image, which is not available for the Windows Server 2022 wave - reason why I chose not to cover it originally.

The Windows image has the same essence of the Server image already discussed above. It's base however, was different and over the time, we decided to reshape that into what is the Server image today. 

If you are a customer using Windows containers for the purposes already explained in the Server image above (Lift and Shift, GPU support, ML, or anything that might need a larger API set from the OS) you have two options:

  • If you are running a Windows Server 2019 or SAC container host, you should use the Windows image.
  • If you are running a Windows Server 2022 container host, you should use the new Server image.

Hopefully that clarifies the use case as well as which image to use on this scenario.

%3CLINGO-SUB%20id%3D%22lingo-sub-2835785%22%20slang%3D%22en-US%22%3ENano%20Server%20x%20Server%20Core%20x%20Server%20-%20Which%20base%20image%20is%20the%20right%20one%20for%20you%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2835785%22%20slang%3D%22en-US%22%3E%3CP%3EAlmost%20every%20week%20I'm%20faced%20with%20this%20question%20from%20customers%3A%20Which%20Windows%20base%20container%20image%20is%20the%20right%20one%20for%20me%3F%20For%20that%20reason%2C%20I%20decided%20to%20write%20this%20blog%20post%20to%20help%20customers%20understand%20the%20differences%20between%20the%20three%20Windows%20container%20base%20images%2C%20its%20use%20cases%2C%20and%20pros%20and%20cons%20from%20each%20one.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBefore%20we%20get%20started%2C%20it's%20important%20to%20note%20that%20in%20many%20cases%2C%20there%20is%20a%20framework%20image%20that%20leverages%20these%20images%20above.%20The%20most%20common%20examples%20are%20%3CA%20href%3D%22https%3A%2F%2Fhub.docker.com%2F_%2Fmicrosoft-dotnet-framework%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E.Net%20Framework%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Fhub.docker.com%2F_%2Fmicrosoft-dotnet-framework-aspnet%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EASP.%20Net%3C%2FA%3E%2C%20.%3CA%20href%3D%22https%3A%2F%2Fhub.docker.com%2F_%2Fmicrosoft-dotnet%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3ENet%3C%2FA%3E%20(formerly%20.Net%20Core)%2C%20among%20many%20others.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EWhat%20are%20the%20base%20container%20images%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EBase%20images%20are%20used%20(as%20the%20name%20suggests)%20as%20basis%20for%20the%20framework%20and%20application%20you%20want%20to%20host.%20They%20dictate%20which%20OS%20APIs%20are%20available%20for%20your%20application%20and%20it%20could%20be%20a%20large%20or%20a%20small%20set%20of%20APIs.%20The%20more%20APIs%20are%20available%2C%20the%20more%20binaries%20are%20needed%2C%20resulting%20in%20a%20larger%20base%20image.%20For%20that%20reason%2C%20when%20we%20started%20to%20produce%20these%20base%20images%20we%20had%20Server%20Core%20and%20Nano%20Server%2C%20with%20the%20Server%20image%20being%20added%20later%20to%20address%20scenarios%20not%20supported%20by%20the%20former%20images.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22LTSC2022%20Images.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316924i1942348B2559051F%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22LTSC2022%20Images.png%22%20alt%3D%22LTSC2022%20Images.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3ENano%20Server%20base%20container%20image%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EThis%20is%20our%20smallest%20base%20container%20image.%20As%20mentioned%20above%2C%20this%20means%20less%20APIs%20available.%20For%20Nano%20Server%2C%20we%20focused%20on%20scenarios%20where%20developers%20will%20be%20writing%20new%20applications%20on%20which%20the%20framework%20can%20target%20the%20specific%20APIs%20of%20Nano%20Server.%20Examples%20of%20frameworks%2C%20languages%2C%20or%20apps%20that%20are%20supported%20on%20Nano%20Server%20are%20.Net%20Core%20(now%20called%20.Net)%2C%20Apache%2C%20NodeJS%2C%20Phyton%2C%20Tomcat%2C%20Java%20runtime%2C%20JBoss%2C%20Redis%2C%20among%20others.%3C%2FP%3E%0A%3CP%3EOnce%20pulled%20and%20extracted%2C%20the%20Nano%20Server%20base%20image%20has%20around%20290MB%20in%20size.%20That%20means%20its%20pull%20time%20is%20extremely%20fast%2C%20allowing%20for%20faster%20scale-up%20processes.%20The%20other%20side%20of%20this%20is%20the%20already%20mentioned%20requirement%20that%20only%20specific%20frameworks%20will%20be%20supported%20in%20this%20base%20image.%3C%2FP%3E%0A%3CP%3ETo%20provide%20some%20history%2C%20the%20Nano%20Server%20is%20actually%20based%20on%20a%20previously%20available%20Nano%20Server%20installation%20option.%20We%20discontinued%20this%20option%20a%20few%20years%20ago%20specifically%20to%20focus%20on%20the%20Nano%20Server%20base%20container%20image.%26nbsp%3BOverall%2C%20the%20general%20question%20I%20recommend%20customers%20to%20ask%20when%20developing%20new%20applications%20is%20to%20always%20check%20if%20the%20Nano%20Server%20provides%20the%20necessary%20APIs%20for%20that%20application.%20If%20so%2C%20choose%20this%20image%20as%20the%20benefits%20of%20a%20smaller%20image%20are%20great.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EServer%20Core%20base%20container%20image%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EIn%20this%20case%2C%20the%20scenario%20expected%20is%20different%20than%20the%20Nano%20Server%20base%20image.%20The%20Server%20Core%20base%20container%20image%20is%20based%20on%20the%20Server%20Core%20installation.%20This%20image%20is%20focused%20on%20lift%20and%20shift%20scenarios%2C%20on%20which%20the%20expectation%20is%20to%20get%20the%20same%20application%20that%20was%20working%20on%20a%20VM%20and%20put%20it%20in%20a%20container%20-%20as%20is%2Fno%20code%20changes.%20Of%20course%20there's%20a%20bunch%20of%20limitations%20here.%20For%20example%2C%20if%20the%20application%20did%20not%20work%20on%20Server%20Core%20already%2C%20it%20most%20likely%20won't%20work%20on%20the%20Server%20Core%20base%20container%20image.%3C%2FP%3E%0A%3CP%3EMore%20importantly%2C%20the%20Server%20Core%20base%20image%20supports%20.Net%20Framework%2C%20which%20is%20the%20framework%20used%20on%20most%20of%20the%20existing%20(not%20to%20say%2C%20legacy)%20applications%20out%20there.%20We%20see%20a%20lot%20of%20customers%20using%20this%20image%20to%20containerize%20applications%20from%20the%20Windows%20Server%202008%20era.%20Not%20surprisingly%2C%20web%20applications%20written%20in%20ASP.Net%203.5.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Server%20Core%20image%20has%20around%204.8GB%20after%20pulled%20and%20extracted%2C%20which%20means%20longer%20pull%20times%2C%20adding%20up%20to%20the%20total%20time%20of%20scale-up%20operations.%20However%2C%20the%20larger%20API%20area%20should%20be%20your%20target%20here.%20Just%20like%20on%20the%20Nano%20Server%2C%20I%20have%20some%20guidance%20on%20this%20image%20I%20provide%20to%20customers%3A%20First%2C%20check%20if%20the%20application%20you're%20trying%20to%20containerize%20works%20on%20regular%20Server%20Core%20deployments.%20If%20not%2C%20containers%20might%20not%20be%20an%20option%20here.%20If%20it%20does%2C%20you%20should%20still%20make%20sure%20you%20try%20out%20the%20application%20on%20a%20Server%20Core%20container%20to%20check%20if%20the%20app%20is%20not%20trying%20to%20use%20something%20from%20the%20OS%20that%20was%20removed%20when%20building%20the%20base%20container%20image.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EServer%20base%20container%20image%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EThis%20is%20our%20largest%20image%2C%20by%20a%20lot%20-%20but%20for%20all%20the%20good%20reasons.%20This%20image%20is%20based%20on%20the%20%22Server%20with%20Desktop%20Experience%22%20installation%20mode.%20Of%20course%2C%20the%20GUI%20is%20not%20present%2C%20but%20the%20UI%20APIs%20are%20there.%20This%20image%20enables%20a%20whole%20new%20set%20of%20scenarios%2C%20including%20support%20to%20GPU%20via%20DirectX.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22GPU_Server2022.png%22%20style%3D%22width%3A%20861px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316823i9771C70AEC530A43%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22GPU_Server2022.png%22%20alt%3D%22GPU_Server2022.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EAnother%20interesting%20scenario%20enabled%20by%20this%20image%20is%20UI%20automation%20tests%20for%20developers.%20As%20mentioned%20before%2C%20you%20don't%20get%20a%20GUI%20with%20this%20image%20-%20rather%2C%20the%20UI%20APIs%20are%20present%20for%20UI%20automation%20tests%20to%20work.%20Also%2C%20some%20UI%20automation%20tools%20might%20not%20be%20supported%20on%20Windows%20containers%20at%20all.%20If%20you%20are%20familiar%20with%20such%20tools%20and%20you%20know%20one%20that%20doesn't%20work%20with%20Windows%20containers%2C%20please%20let%20us%20know%20as%20we're%20interested%20in%20these%20scenarios.%3C%2FP%3E%0A%3CP%3EOf%20course%2C%20the%20compromise%20on%20the%20Server%20image%20is%20the%20total%20size%20of%20around%2011.2GB%2C%20once%20its%20layers%20are%20downloaded%20and%20extracted.%20On%20the%20other%20hand%2C%20think%20of%20this%20base%20image%20as%20your%20an%20alternative%20to%20containerize%20an%20existing%20app%20that%20is%20not%20supported%20on%20Server%20Core.%20The%20question%20I%20ask%20customers%20here%20is%3A%20Does%20the%20app%20works%20on%20Server%20Core%3F%20If%20not%2C%20try%20the%20Server%20image%20as%20that%20should%20probably%20work.%20See%20that%20we%20start%20by%20giving%20the%20Server%20Core%20a%20try%2C%20as%20the%20size%20would%20be%20a%20great%20benefit.%20If%20it%20doesn't%2C%20the%20Server%20image%20should%20do%20the%20work.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EWhy%20not%20say%20the%20exact%20size%20of%20these%20images%3F%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EIt's%20easy%20to%20fall%20on%20the%20temptation%20of%20comparing%20image%20sizes%20for%20comparison%20sake.%20However%2C%20just%20like%20on%20regular%20servers%2C%20you%20should%20not%20simply%20install%20your%20system%20and%20let%20it%20go.%20Containers%20are%20subject%20to%20Patch%20Tuesday%20and%20in%20fact%2C%20Microsoft%20updates%20these%20base%20images%20every%20month%20with%20security%20updates.%20That%20means%20you%20should%20be%20updating%20your%20production%20systems%20composed%20by%20containers%20every%20month%20to%20leverage%20these%20security%20updates.%20The%20way%20you%20perform%20that%20is%20a%20topic%20for%20another%20blog%20post%2C%20but%20the%20point%20here%20is%20that%20given%20these%20monthly%20changes%2C%20the%20size%20of%20the%20base%20container%20images%20will%20vary.%20Some%20months%20we%20gain%20some%2C%20some%20months%20we%20lose%20some.%20The%20fact%20that%20these%20images%20have%20around%20290MB%20(Nano%20Server)%2C%204.8GB%20(Server%20Core)%2C%20and%2011.2GB%20(Server)%20should%20give%20you%20a%20ballpark%20on%20what%20to%20expect%20in%20terms%20of%20size.%20Furthermore%2C%20these%20image%20layers%20are%20compacted%20for%20pulling%20operations%20(download)%20so%20the%20size%20that%20does%20over%20the%20wire%20is%20smaller%20than%20what%20you%20see%20on%20disk.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3ESummary%3C%2FFONT%3E%3C%2FP%3E%0A%3CTABLE%20border%3D%221%22%20width%3D%22100%25%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2225%25%22%3E%26nbsp%3B%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3ENano%20Server%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3EServer%20Core%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3EServer%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3ESize%20(uncompressed%20on%20disk)%3C%2FTD%3E%0A%3CTD%3E~290MB%3C%2FTD%3E%0A%3CTD%3E4.8GB%3C%2FTD%3E%0A%3CTD%3E11.2GB%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2225%25%22%3EBased%20on%20(installation%20mode)%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3ENano%20Server%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3EServer%20Core%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3EServer%20with%20Desktop%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2225%25%22%3EScenarios%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3ENew%20applications%20being%20developed%20for%20Nano%20Server%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3ELift%20and%20Shift%2C%20web%20applications%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3ELift%20and%20Shift%2C%20GPU%20dependent%20apps%2C%20UI%20automation%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2225%25%22%3EExamples%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3E.Net%20(formerly%20.Net%20Core)%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3E.Net%20Framework%2C%20ASP.Net%20Framework%3C%2FTD%3E%0A%3CTD%20width%3D%2225%25%22%3E.Net%20Framework%2C%20DirectX%2C%20ML%20based%20applications%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20always%2C%20let%20us%20know%20if%20you%20have%20questions%20or%20comments%2C%20either%20in%20the%20comments%20section%20below%20or%20in%20our%20GitHub%20repo.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EVinicius%3C%2FP%3E%0A%3CP%3ETwitter%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Fvrapolinario%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%40vrapolinario%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EEdit%3A%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3ESome%20of%20you%20might%20have%20noticed%20I%20left%20the%20already%20known%20%22Windows%22%20image%20out%20of%20the%20article.%20That%20was%20on%20purpose%2C%20but%20I%20wanted%20to%20comment%20on%20that%20image%20so%20it%20doesn't%20create%20any%20confusion%20for%20current%20customers.%20Currently%2C%20Microsoft%20has%204%20main%20base%20images%20for%20Windows%20containers%2C%20the%20already%20covered%20Nano%20Server%2C%20Server%20Core%2C%20and%20Server.%20The%20last%20one%20is%20the%20Windows%20image%2C%20which%20is%20not%20available%20for%20the%20Windows%20Server%202022%20wave%20-%20reason%20why%20I%20chose%20not%20to%20cover%20it%20originally.%3C%2FP%3E%0A%3CP%3EThe%20Windows%20image%20has%20the%20same%20essence%20of%20the%20Server%20image%20already%20discussed%20above.%20It's%20base%20however%2C%20was%20different%20and%20over%20the%20time%2C%20we%20decided%20to%20reshape%20that%20into%20what%20is%20the%20Server%20image%20today.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20are%20a%20customer%20using%20Windows%20containers%20for%20the%20purposes%20already%20explained%20in%20the%20Server%20image%20above%20(Lift%20and%20Shift%2C%20GPU%20support%2C%20ML%2C%20or%20anything%20that%20might%20need%20a%20larger%20API%20set%20from%20the%20OS)%20you%20have%20two%20options%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20are%20running%20a%20Windows%20Server%202019%20or%20SAC%20container%20host%2C%20you%20should%20use%20the%20Windows%20image.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20are%20running%20a%20Windows%20Server%202022%20container%20host%2C%20you%20should%20use%20the%20new%20Server%20image.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EHopefully%20that%20clarifies%20the%20use%20case%20as%20well%20as%20which%20image%20to%20use%20on%20this%20scenario.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2835785%22%20slang%3D%22en-US%22%3E%3CP%3EAlmost%20every%20week%20I'm%20faced%20with%20this%20question%20from%20customers%3A%20Which%20Windows%20base%20container%20image%20is%20the%20right%20one%20for%20me%3F%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2835785%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Econtainers%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Edocker%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Oct 13 2021 03:04 PM
Updated by: