-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
docker-agent windowsservercore-ltsc2019
images use a windowsservercore-1809
as base image
#475
Comments
windowsservercore-ltsc2019
images use a windowsservercore-1809
as base image instead of -ltsc2019
windowsservercore-ltsc2019
images use a windowsservercore-1809
as base image
It appears that like Eclipse, Microsoft didn't publish any
Closing this issue. |
As I'm working on #349 in #459 it appears to me there are no Thus we don't currently have a "proper" docker-agent @timja @slide @jenkinsci/team-docker-packaging WDYT about switching the base images from
https://mcr.microsoft.com/v2/windows/servercore/tags/list |
If Microsoft is not supporting an image for it, we probably shouldn't support it either, but I'm fine if someone wants to put in the work to get it working. |
Sounds good to me |
Someone who just has been bitten by this: https://community.jenkins.io/t/updating-powershell-7-version-included-with-jenkins-agent-docker-image/8691 (their Powershell version depends on the |
Jenkins and plugins versions report
ci.jenkins.io
What Operating System are you using (both controller, and any agents involved in the problem)?
N/A
Reproduction steps
Before the recent refactoring there was
docker-agent/windows/windowsservercore-ltsc2019/Dockerfile
Line 26 in bd84740
(It's still the case, the refactoring hasn't changed any thing in the artifacts generated)
Expected Results
docker-agent
windowsservercore-ltsc2019
images use awindowsservercore-ltsc2019
as base image.Actual Results
docker-agent
windowsservercore-ltsc2019
images use awindowsservercore-1809
as base image.Anything else?
No response
The text was updated successfully, but these errors were encountered: