dduportal
commented
1 year ago Alas the flags -SwitchDaemon (etc.) are Docker Desktop only si it's not an option today on the Jenkins Infrastrcuture which uses Windows Server VMs.
As per https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment, Docker Desktop is recommended on Windows 10/11 and Docker CE standalone (or Mirantis or containerd) on Windows Server 2016/2019/2022.
It means that, in order to cover the CI case of "Windows build with Linux container", we need to use one of the following solutions:
-
Define a new kind of VM with a Windows 11 + Docker Desktop to replace existing Windows images
- ✅ Allows user
jenkinsswitching from/to Linux Container - ✅ Closer environment to contributors
- ❌ Slower Windows container (due to Hyper V isolation instead of native container isolation used on Windows Server)
- ❌ Need to keep maintaining Windows containers images for usage in ACI/Kubernetes that must be Windows Server
- ✅ Allows user
-
Define a new kind of VM with a Windows 11 + Docker Desktop to next to existing Windows images
- ✅ Allows user
jenkinsswitching from/to Linux Container - ✅ Closer environment to contributors
- ❌ Need to keep maintaining 3 kinds of Windows templates
- ❌ Need to add a whole new set of labels on ci.jenkins.io
- ✅ Allows user
-
(if it works: nested virtualization is to be checked) Define a new kind of VM with a Windows Server + WSL (to provide Docker containers) next to existing Windows images
- ✅ Provides a Linux container in Windows environment as expected
- ✅ Easier to maintain as it would be a minor variation of the existing templates
- ❌ Suffers from the hiccups of WSL (bind mounts particularly that can act weirdly) and nested virtualization slowness
- ❌ Need to keep maintaining 3 kinds of Windows templates
- ❌ Need to add a whole new set of labels on ci.jenkins.io
if you have any other idea, please share!
Service(s)
ci.jenkins.io
Summary
It is not uncommon for a plugin to have some containers for tests and use the legacy
docker-fixturesorTestContainersHowever the containers are generally linux specific (e.g.
--platform=linux) and this causes build errors when run on windows VMs.As it is useful to run the tests on Windows as well as Linux it would be helpful if there was a Windows VM that had been set to Linux containers (rather than the current Linux containers).
Current workaround is to use a specific container label in the
buildPlugins(which actually broke and was just fixed a few hours ago)e.g. https://github.com/jenkinsci/distfork-plugin/blob/master/Jenkinsfile https://github.com/jenkinsci/docker-workflow-plugin/blob/d5d2e5c4007f7ea006152542b2bcbe0f1b2b08aa/Jenkinsfile#L1-L4 are 2 plugins that use this approach.
a windows VM can be switched between linux and windows containers with the command
"c:\Program Files\Docker\Docker\DockerCli.exe" -SwitchDaemonuntested (the help is broken) but
-SwitchLinuxEnginemay switch specifically to linux and-SwitchWindowsEnginemay likewise do the same for windows containers.Reproduction steps
No response