Skip to content

Issue to track 20H2 support #552

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks
anamnavi opened this issue Apr 12, 2021 · 11 comments · Fixed by #578
Closed
2 tasks

Issue to track 20H2 support #552

anamnavi opened this issue Apr 12, 2021 · 11 comments · Fixed by #578
Assignees

Comments

@anamnavi
Copy link
Member

anamnavi commented Apr 12, 2021

This issue will track when full windows 20H2 support will be back and we can publish those images to ACR. At the moment, we have provided images and corresponding dockerfiles for nanoservercore and windowsservercore 20H2 distributions but can't publish it to ACR.

An issue has been created on the ACR repo too: Azure/acr#532

Check list

@ghost ghost added the Needs: Triage 🔍 label Apr 12, 2021
@ghost ghost assigned TravisEz13 Apr 12, 2021
@anamnavi anamnavi self-assigned this Apr 12, 2021
@anamnavi anamnavi mentioned this issue Apr 12, 2021
8 tasks
@TravisEz13
Copy link
Member

TravisEz13 commented Apr 12, 2021

Added known issue:
https://github.com/PowerShell/PowerShell-Docker/wiki/Known-Issues#windows-20h2-images-and-newer

GitHub
Repository for building PowerShell Docker images. Contribute to PowerShell/PowerShell-Docker development by creating an account on GitHub.

@vboulineau
Copy link
Contributor

@anamnavi @TravisEz13 Any news on this? I see that LTSC 2022 has been released, so I guess it's supported in ARC. It'd be nice to support the last SAC as well.

@TravisEz13
Copy link
Member

We have images available for ltsc2022. You'll have to ask ACR about their plan to release support for ltsc2022. We have moved to an internal preview environment to get support early.

@TravisEz13
Copy link
Member

@anamnavi plans to add 20H2 images soon.

@GrumpyMeow
Copy link

I find it quite unfortunate that there's no news on this subject. It feels like ACR is lagging behind and will become end-of-life.

ltsc2022: Pulling from windows/servercore
no matching manifest for windows/amd64 10.0.19041 in the manifest list entries
20H2: Pulling from windows/servercore
no matching manifest for windows/amd64 10.0.19041 in the manifest list entries

@TravisEz13
Copy link
Member

TravisEz13 commented Sep 23, 2021

@GrumpyMeow We can support 2022, feel free to submit a PR.

Update (2021-10-03):
looking at your ask again, you are trying to run thing on 20H1, you can't run newer versions on an older host on Windows.

@vboulineau
Copy link
Contributor

vboulineau commented Sep 24, 2021

@TravisEz13 ltsc2022 is already published on DockerHub, but still nothing for 20H2. It's not great because 20H2 starts to be used as current SAC by multiple providers, like GKE: https://cloud.google.com/kubernetes-engine/docs/how-to/creating-a-cluster-windows#1.20

Google Cloud

@TravisEz13
Copy link
Member

@vboulineau, Great, feel free to submit a PR. We are still working on getting 2022 support fully out. We'll work back from there as time allows.

cc @anamnavi, I don't know if you have time to add 20H2 images.

@vboulineau
Copy link
Contributor

I think the misunderstanding came from ACR support: it does now support up to Windows 2022 (with all versions in between), not only 2022. I've opened the PR to remove the BrokenFlag for 20H2 and hopefully it should build successfully.

@vboulineau
Copy link
Contributor

vboulineau commented Oct 5, 2021

Thanks for merging the PR quickly. Is the image publication to mcr.microsoft.com automated? Because I don't see the tags there yet: https://mcr.microsoft.com/v2/powershell/tags/list

I wonder if I did not miss to update release/servicing/windowsservercore/getLatestTag.ps1

@TravisEz13
Copy link
Member

getlatesttag.ps1 shouldn't be used anymore. I think it should all be released now. We aren't allowed to automatically trigger off PR merges. We usually release a few days after the second Tuesday of the month.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants