-
Notifications
You must be signed in to change notification settings - Fork 240
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
backport: Windows HPC base image (#3105) #3270
Open
rbtr
wants to merge
1
commit into
release/v1.5
Choose a base branch
from
backport/v1.5/win-hpc
base: release/v1.5
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rbtr
requested review from
a team,
camrynl,
paulyufan2,
ashvindeodhar and
thatmattlong
as code owners
December 13, 2024 23:52
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
rbtr
added
cns
Related to CNS.
npm
Related to NPM.
cni
Related to CNI.
dependencies
Dependencies only.
windows
release/1.5
Change affects v1.5 release train
labels
Dec 13, 2024
thatmattlong
approved these changes
Dec 16, 2024
jpayne3506
approved these changes
Dec 16, 2024
jpayne3506
approved these changes
Dec 16, 2024
rbtr
force-pushed
the
backport/v1.5/win-hpc
branch
from
December 16, 2024 22:14
5bc83dd
to
db57913
Compare
This pull request is stale because it has been open for 2 weeks with no activity. Remove stale label or comment or this will be closed in 7 days |
Signed-off-by: Evan Baker <[email protected]>
rbtr
force-pushed
the
backport/v1.5/win-hpc
branch
from
January 3, 2025 18:34
db57913
to
e42b448
Compare
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
cni
Related to CNI.
cns
Related to CNS.
dependencies
Dependencies only.
npm
Related to NPM.
release/1.5
Change affects v1.5 release train
windows
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Windows HPC are special.
They explicitly do not run in a chroot or similar execution sandbox, and their filesystem is a merged view of the hostfs and their shipped containerfs. This means that we don't need to ship a filesystem: we recently moved from servercore to nanoserver and observed that the lack of pwsh.exe in nanoserver is manageable (in containerd 1.7+, automatically, and in 1.6, by tweaking the container PATH). We can go further and remove the rest of the OS since, as HPC, we don't need it and can escape to the hostfs for dependencies like powershell.
Further, HPC do not have the containerd/containerd#7431 (the "os-version") as regular Windows containers - any Windows HPC may run on any Windows Server Host (given the executables are compatible with that Host).
In some of the testing with WS25 we have seen that this may happen - it was observed that containerd on WS25 inconsistently fetched the WS25 CNI image specified in our multiplatform manifest but was able to run other WS images without any issue.
Containerd >= 1.6 containerd/containerd#8101, so we don't need to build separate Windows images for all of our target WS variants and can simply build one without that extra metadata.