-
Notifications
You must be signed in to change notification settings - Fork 287
HostProcess containers with Hypervisor Isolation #2531
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
Merged
rawahars
merged 13 commits into
microsoft:main
from
rawahars:hpc_inboc_hcs_for_hypervisor_isolation
May 22, 2026
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
f76b015
Added support for hypervisor isolated hpc
rawahars 717bd1f
Added unit tests for HostProcess Container helper methods
rawahars ac5a240
Added unit tests for updateConfigForHostProcessContainer method
rawahars 6a5350d
Added unit tests for handleProcessArgsForIsolatedJobContainer
rawahars bf8fd03
Rectified the schema for custom rootfs for HCS HPCs
rawahars 311a8bb
Rectified the logic for user inherit functionality for HPCs
rawahars e43d8d2
Addressed PR feedback
rawahars de2dcdf
Schema changes inline with HCS
rawahars 4916a30
review comments 2
rawahars 9dfb4cb
reject task creation if the UVM does not support HPCs
rawahars d209636
allow HPCs in any UVM
rawahars 930adcd
HPC: tighten inherit-user scoping, harden cmd-wrapping, and fix path …
rawahars bcac42c
address review comments 2
rawahars File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this part of it special for HPC? I dont get it, this is true for all Windows containers right? At this point its just another container
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's specific to HostProcess containers because of when the process is joined to the silo.
For a normal WCOW container (process- or Hyper-V-isolated), the guest creates the workload process from inside the container silo, so
CreateProcessresolves the image name andPATHusing the silo's filesystem view — the bind-mounted rootfs, the container'sSystem32, etc. A bare echo / dir or a binary that lives only in the rootfs works fine because the silo is already in scope at creation time.For a HostProcess container the process is created outside the silo and only assigned to the silo's job object after the fact. That means image-name resolution happens against the launcher's view (host/UVM System32, Windows, host PATH), not the container's rootfs. Shell builtins (echo, set, redirection, …) and any rootfs-only executable would fail with ERROR_FILE_NOT_FOUND.
Wrapping with
cmd /csidesteps this:cmd.exeis guaranteed to exist under the launcher'sSystem32, and once it's joined to the silo it runs inside the container's filesystem view, where it can resolve builtins and rootfs-relative paths normally. Regular WCOW containers don't need this because they never have that"created outside, joined after"gap.