Skip to content

windows: add ltsc releases as default bases #575

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cpuguy83
Copy link
Member

@cpuguy83 cpuguy83 commented Mar 17, 2025

This makes it so that, by default, windowscross/container will build for
all current ltsc releases.

@cpuguy83 cpuguy83 requested a review from a team as a code owner March 17, 2025 19:12
@cpuguy83 cpuguy83 force-pushed the windows_default_multi branch 3 times, most recently from dc0c409 to b2ee90f Compare March 17, 2025 19:49
@cpuguy83 cpuguy83 changed the title windows: add ltsc2019 to list of default base images windows: add ltsc releases as default bases Mar 17, 2025
This makes it so that, by default, windowscross/container will build for
all current ltsc releases.

Signed-off-by: Brian Goff <[email protected]>
@cpuguy83 cpuguy83 force-pushed the windows_default_multi branch from b2ee90f to 998b17a Compare March 22, 2025 20:09
@@ -22,10 +22,21 @@ import (
)

const (
defaultBaseImage = "mcr.microsoft.com/windows/nanoserver:1809"
winltsc2019 = "mcr.microsoft.com/windows/nanoserver:ltsc2019"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: ltsc2019 and 1809 are the same images.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe add a comment about this?

Copy link
Contributor

@adamperlin adamperlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cpuguy83 it looks like there are some CI failures, possibly to do with an image config issue?

@cpuguy83
Copy link
Member Author

@cpuguy83 it looks like there are some CI failures, possibly to do with an image config issue?

Failures are due to using SingleRef() in tests where we are no longer producing just a single ref since there are multiple images in the result.

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

Successfully merging this pull request may close these issues.

3 participants