Self build base OS images

[alphagocc]

What is your question? I'm wondering how to make a windows base OS image. My OS version is Windows 11 22H2, but there isn't any suitable image for the system. Images with low version prevents me from using process isolating containers on my PC.

[vitaliy-leschenko]

You have to use Windows Server 2022 images. Windows 11 supports to run it in hyperv and process isolation level.

[alphagocc]

I've tried both Windows Images and Windows Server image. With some hacks (change the version in the mainifest to a higher version) I successfully started a nanocore:ltsc2022 container, but I am still unable to start any other images. For more specific, my windows version is 22622.436

So I decide to ask if there is any way to produce a base os image by myself and there won't be any compatibility issues.

[fady-azmy-msft]

Hey @alphagocc, can you explain what you mean by changes to the manifest? And can you share the errors you're seeing?

[alphagocc]

@fady-azmy-msft Error is no match for platform in manifest: not found (by nerdctl)

Edit platform>os.version to host os version can successfully start the nanoserver container

[alphagocc]

By the way, I also support this guy https://github.com/microsoft/Windows-Containers/issues/222#issuecomment-1162118376 I think we need a tool to remove container image dependency from Microsoft

[fady-azmy-msft]

I see. Can you share the repro steps you took that caused the error?

[ghost]

This issue has been open for 30 days with no updates. , please provide an update or close this issue.

[alphagocc]

I see. Can you share the repro steps you took that caused the error?

nerdctl.exe run --rm mcr.microsoft.com/windows/nanoserver:ltsc2022 windows-test cmd /c "echo Hello World!"

[smallmodel]

About the author question of making a base OS image, it would be great if one could generate a container image from the host. I made a POC that does this (process isolation mode only, tested on Windows 11 - 10.0.22000) : https://github.com/Ley0k/wincon it's not usable in production, and I didn't try with Docker, but actually a proof that it could work by just generating registry hives and linking host files.

[ohault]

This is a very good and strategic question, see also https://github.com/microsoft/Windows-Containers/issues/291

[fady-azmy-msft]

@Juarezhm, any thoughts on this?

[ghost]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[ohault]

For clarification, I guess here we are talking about Windows container base image sizes in MB and not in GB.

How to create such minimal base image from witch all larger images could be created by adding components and configurations ?

This should provide a way to create the same exact images currently provided by Microsoft like Nano Server, Server Core, Windows and Windows Server, but in full transparency according to good compliance practices.

This is basically a lean approach, as existing in the embedded industry for decades.

[slonopotamus]

all larger images could be created by adding components and configurations

I doubt anything will happen here given that Windows itself is not modular.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[ohault]

This is a very good and important question. So far, we have seen so few blog posts about what is going on with Windows Containers. Windows Containers are also still facing huge architectural challenges and very poor technical documentations in term of software design and almost no public roadmap! It's time to wake up!

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[ohault]

Despite the fact that the Ignite 2023 conference was one of the best Microsoft conferences since PDC 2000, it can be found very unfortunate that Microsoft has still not been able to clearly communicate a technical roadmap for the future Windows containers!

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.

[microsoft-github-policy-service[bot]]

This issue has been open for 30 days with no updates. @Juarezhm, please provide an update or close this issue.