Forum Discussion
Solved
Windows Server 2022 container base images?
With the removal of the Windows Server 2022 Insider Preview (build 20344), we have lost the only currently possible to validate process-isolated containers for Windows Server 2022. Is there a pla...
- HampyWG - Thanks for bringing this to our attention. Now we have published Windows Server 2022 Preview build 20348 container images:
https://hub.docker.com/_/microsoft-windows-servercore-insider/
https://hub.docker.com/_/microsoft-windows-nanoserver-insider
https://hub.docker.com/_/microsoft-windows-server-insider
Feel free to join the discussion with the Tweets I posted: https://twitter.com/WeijuanLand/status/1421166335132798977.
HampyWG - Thanks for bringing this to our attention. Now we have published Windows Server 2022 Preview build 20348 container images:
https://hub.docker.com/_/microsoft-windows-servercore-insider/
https://hub.docker.com/_/microsoft-windows-nanoserver-insider
https://hub.docker.com/_/microsoft-windows-server-insider
Feel free to join the discussion with the Tweets I posted: https://twitter.com/WeijuanLand/status/1421166335132798977.
https://hub.docker.com/_/microsoft-windows-servercore-insider/
https://hub.docker.com/_/microsoft-windows-nanoserver-insider
https://hub.docker.com/_/microsoft-windows-server-insider
Feel free to join the discussion with the Tweets I posted: https://twitter.com/WeijuanLand/status/1421166335132798977.
Weijuan Shi Davis Thank you for publishing those images.
I'm concerned that the Feedback Hub issue I raised weeks ago, despite being the place we were directed to send issue reports for non-Insider builds, seems to have seen no action, but a post here was apparently resolved overnight.
There's also been https://github.com/microsoft/Windows-Containers/issues/117 which touched these images being missing a week ago, although it wasn't the main point of the issue, so I can see how it might have been overlooked.
Should I ignore Feedback Hub (and the instructions in the Preview announcement) and keep raising issues here?
- Sorry for the inconvenience and not catching this problem early. It's a human error that I didn't know 20348 is the build of the eval until Mary forwarded me this thread. I also wanted to be honest that today I don't monitor either the Feedback Hub or here. I encourage you to report issues on containers at our GitHub community: https://github.com/microsoft/Windows-Containers/issues. We do monitor there (even though we might be slow :)). Or you can find me on Twitter @WeijuanLand. Or email us at win-customers@microsoft.com.
- Thank you for your reply and clarification.
I hadn't raised this as an issue on GitHub or here (even though I've raised _other_ issues on that GitHub project...) until last week because I had understood the announcement to mean that Server 2022 issues should be preferred to go via Feedback Hub, and I didn't want to be "that person" who shows up in every tangential thread and forum to cross-post about their specific issue.
I'll focus feedback onto the Windows-Containers GitHub project for now, since that seems to be the monitored and focussed location. I don't mind slow, this wasn't a blocking issue for the past few weeks, until I learned that the 20344 ISOs had been pulled.
That said, _someone_ should probably monitor Feedback Hub. There's a specific *Windows Server > Containers* section, and if that's not being checked, it might be better to remove it to avoid confusion in future. Most of the things there aren't Containers related, a fair few seemed to be related to NvContainer. NvContainer is part of the Nvidia graphics driver install and unrelated to Windows Containers.