3 ms·
Windows containers are a thing, and MS has "Nano Server" base image. Back in the day, MS did even release Nano Server as a standalone OS, from what I gather it
by zokier 1y ago
Windows containers are a thing, and MS has "Nano Server" base image.
Back in the day, MS did even release Nano Server as a standalone OS, from what I gather it was generally <500MB. Pretty decent for a Windows you could actually run applications on.
- esseph 1y ago> Windows containers Are people using these in production? I assume so, with libvirt handling them on k8s for a vmware transition option.
- nikanj 1y agoYes, if by people you include Azure in-house engineering teams
- actionfromafar 1y agoI will allow it, once.
- tecleandor 1y agoAlthough I don't manage those, I've seen them at work. Running on EKS Windows nodes, for dotnet and SQL Server loads.
- p_l 1y agoOh Nano Server, that's a blast from the past. I worked on porting certain Software Defined Networking product to Windows platform, for use with Hyper-V. Nano Server was new and we tried to target it as one of the options, especially since it was implied to be recommended way to deploy Hyper-V hosts. And yes, IIRC it took less than 500MB, but it couldn't run most windows applications (for example, GUI was missing). So much was stripped out that at one point I ended up with reverse-engineered Windows Update packaging (unfortunately lost my notes) because the oldest form of Windows Installer, the one used with INF files for drivers, could not be used fully - specifically, we could not run any kind of action in our own DLL when initializing the drivers. And messing with the right registry keys was fraught with peril. Do not recall all issues, but essentially we were trying to create a package that could be applied with DISM.EXE onto Nano Server image.