Windows support

[jsturtevant]

Currently we cannot use this project on Windows. This is an umbrella issue to track Windows support. There may be more items added as the work progresses.

The project doesn't currently build: it builds since #238 🎉

 cargo build
   Compiling zstd-safe v5.0.2+zstd.1.5.2
   Compiling zstd-sys v2.0.4+zstd.1.5.2
   Compiling ittapi-sys v0.3.2
   Compiling wasmtime-runtime v2.0.2
   Compiling cranelift-wasm v0.89.2
   Compiling psm v0.1.21
   Compiling uapi v0.2.10
   Compiling uapi-proc v0.0.5
   Compiling num-traits v0.2.15
   Compiling ttrpc v0.6.1
   Compiling ittapi v0.3.2
   Compiling cap-fs-ext v0.26.1
error[E0425]: cannot find function `geteuid` in crate `libc`
   --> C:\Users\jstur\.cargo\registry\src\github.com-1ecc6299db9ec823\uapi-proc-0.0.5\src\lib.rs:16:34
    |
16  |             root: unsafe { libc::geteuid() == 0 },
    |                                  ^^^^^^^ help: a function with a similar name exists: `getpid`

Some errors have detailed explanations: E0412, E0422, E0425, E0432, E0433.
For more information about an error, try `rustc --explain E0412`.
error: could not compile `ttrpc` due to 58 previous errors
error: failed to run custom build command for `uapi v0.2.10

At a minimum the following tasks need to be completed:

• Windows support ttrpc-rust#132
  • implementation in Windows Support for Sync implementation ttrpc-rust#172
• Will the rust-extensions support Windows? rust-extensions#4
  • Windows support for the synchronous shim rust-extensions#139
• Ensure can build and run test image on windows
  • Import base layer images microsoft/hcsshim#1688
  • Figure out how to remove platform specific files from docker images deislabs/containerd-wasm-shims#89
    • can be solved via: fix(spin/certs): inject CA bunde in the filesystem spinkube/spin-operator#184
  • Distribute using OCI artifacts / allow shim to pull artifact #108
  • proposal for WASI image in containerd: https://docs.google.com/document/d/11shgC3l6gplBjWF1VJCWvN_9do51otscAm0hBDGSSAc/edit
    • Handle Wasm Images with wasm media types #147
    • Add support for pulling Wasm OCI artifacts containerd#8699
• Support in runwasi
  • refactor usage of nix in runwasi
    • Refactor use statements to enable building Windows #238
    • turn linters on Refactor use statements to enable building Windows #238 (comment)
  • refactor the cgroup setup to run only on Windows our cgroup support was removed feat: remove cgroups implementation #221
  • Add Windows e2e tests
  • enable this test on Windows.
  • convert harded coded sockets to named pipes on windows for instance
  • Upgrade to protobuff 3.x - Update project to latest shim-protos and ttrpc using protobuf 3.x #81
  • Do not panic if windows.layerFolder is null youki-dev/oci-spec-rs#127 :

    runwasi/crates/containerd-shim-wasm/src/sandbox/manager.rs

    Line 207 in 514235e

    let client = Client::connect("unix:///run/io.containerd.wasmtime.v1/manager.sock")?;

  • (low priority) Add ability to parse and layout file system. May not be needed since, we've moved to WASM OCI images which means containerd provides a blank disk and can solve other file system deps with https://github.com/bytecodealliance/wasi-virt. Need to looking to see if scratch space is expected?
  • Add shim implementations
    • poc - jsturtevant@5ca95bb
    • launch shim as separate job process and load the OCI layers
    • Likely require some of the work in https://github.com/jsturtevant/power-process to launch job object with Arg zero
  • Support client create on Windows rust-extensions#205 - needed to load wasm modules from containerd
  • Add network namespace logic
    • using https://github.com/jsturtevant/hcn-rs see jsturtevant@5ca95bb

[squillace]

thanks, @jsturtevant !!!

[jsturtevant]

This is the PR that enables can import the test image to windows (microsoft/hcsshim#1688)

[jsturtevant]

When parsing the runtime spec in runwasi it fails, tracking in youki-dev/oci-spec-rs#126

[squillace]

@jsturtevant this is great work, man

[jprendes]

To add to the TODO list, enable this test on Windows.

[liangchenghao1]

@jsturtevant Hi, I am working on creating a wasm container on a Windows node using runwasi.
I see that the key tasks listed in this issue have been basically solved, may I ask whether the wasm application under Windows can be preliminarily implemented now? If not, what are the key remaining issues?
Looking forward to your reply.

[jsturtevant]

@liangchenghao1 Thanks for the interest, I've been side tracked with other work but I've updated the todo, list with the last items. remaining.