Skip to content
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

Add nanoserver ltsc2019 along with 1809 #451

Closed
dduportal opened this issue Jul 6, 2023 · 2 comments · Fixed by #459 or #488
Closed

Add nanoserver ltsc2019 along with 1809 #451

dduportal opened this issue Jul 6, 2023 · 2 comments · Fixed by #459 or #488

Comments

@dduportal
Copy link
Contributor

dduportal commented Jul 6, 2023

What feature do you want to see added?

As per https://learn.microsoft.com/en-us/windows-server/get-started/servicing-channels-comparison and https://hub.docker.com/_/microsoft-windows-nanoserver, we should provide an LTSC2019 for nanoserver in replacement of 1809.

That would ensure our users always have the latest stable content from the OS base image, ant it would help us for maintenance (ref. https://github.com/jenkinsci/docker-agent/pull/445/files#r1254304996 for instance).


This would impact the published tags by changing the suffix 1809 by ltsc2019.

It means we also want to introduce a set of (additional) new tags such as jdk11-nanoserver, 3107.v665000b_51092-16-jdk11-nanoserver, etc. like we are already doing with the Linux image while keeping the existing ones.

Note that https://docs.docker.com/compose/compose-file/build/#tags could GREATLY help in that matter

@dduportal dduportal changed the title Use nanoserver ltsc2019 instead of 1809 Add nanoserver ltsc2019 along with 1809 Jul 28, 2023
@dduportal
Copy link
Contributor Author

Editing issue title: we want both 1809 (to keep existing images) in addition to the new ltsc2019.

@lemeurherve
Copy link
Member

lemeurherve commented Sep 4, 2023

Reopening as the suggestion done in #475 for adding it in another PR hasn't been applied.

Should be closed by #488

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