Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

feature: cross-container named pipes #2358

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

anmaxvl
Copy link
Contributor

@anmaxvl anmaxvl commented Jan 22, 2025

Add new "uvm://" mount prefix to support cross-container
pipes for Xenon WCOW containers. For now, it's a WCOW-only
feature, while the Linux work is being prototyped.

Additionally, extend the logic of GetContainerPipeMapping to
also handle cross-container pipes within the UVM. The syntax
similar to sandbox mounts:

{
  "host_path": "uvm://\\\\.\\pipe\\uvmPipe",
  "container_path": "\\\\.\\pipe\\containerPipe"
}

Containers sharing the pipe need to have the same "host_path".

@anmaxvl anmaxvl force-pushed the hyperv-wcow-cross-container-pipes branch from e1ff3a9 to ab27eeb Compare March 3, 2025 09:57
Add new "uvm://" mount prefix to support cross-container
pipes for Xenon WCOW containers. For now, it's a WCOW-only
feature, while the Linux work is being prototyped.

Additionally, extend the logic of `GetContainerPipeMapping` to
also handle cross-container pipes within the UVM. The syntax
similar to sandbox mounts:

```
{
  "host_path": "uvm://\\\\.\\pipe\\uvmPipe",
  "container_path": "\\\\.\\pipe\\containerPipe"
}
```

Containers sharing the pipe need to have the same "host_path".

Signed-off-by: Maksim An <maksiman@microsoft.com>
@anmaxvl anmaxvl force-pushed the hyperv-wcow-cross-container-pipes branch from ab27eeb to cc4d581 Compare March 3, 2025 11:02
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant