-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
fix: Upgrade windows container to ltsc2022 #11246
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you try trigger a release build but only builds the image? https://github.com/argoproj/argo-workflows/blob/master/.github/workflows/release.yaml
I don't have permissions to do that. |
You can comment out most of it and only runs a docker build on Windows. You can run modify it to run it in your fork too |
This PR remains in draft for now, but I have something working @terrytangyuan if you wish to test:
|
Signed-off-by: Tim Collins <[email protected]>
…er version Signed-off-by: Tim Collins <[email protected]>
If it's working, we can merge it. Let me know when ready. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Validated on our fork
Moving back to draft. The pull test failed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Passing now. Thanks!
Err. It's not. But... ok? |
Signed-off-by: Tim Collins <[email protected]>
Signed-off-by: Tim Collins <[email protected]> Signed-off-by: Jeremy Hager <[email protected]>
Signed-off-by: Tim Collins <[email protected]>
Signed-off-by: Tim Collins <[email protected]> Signed-off-by: Dillen Padhiar <[email protected]>
Fixes #10738
and the fact that Windows builds were not releasing.
Older builds were on the 1809 container, which isn't supported any more. Chocolatey recently dropped support and this is what killed the build.
The container we are replacing went out of Microsoft support in November 2020, so this shouldn't be a huge surprise for Windows users: https://learn.microsoft.com/en-us/lifecycle/announcements/windows-10-1809-end-of-servicing
Motivation
Updates to a supported version of Windows and allows the release mechanism to work again.
Modifications
I'm not super familiar with how windows containers work (if they do at all :p) but I think this now means that workflows will only run on server 2022 - it looks like containers are pinned to their host in the least containery-way possible. So this probably requires a minor release of Workflows, not a patch.
Verification
Built on the Pipekit fork and released as mentioned below in the comments.