Ian King'ori
Ian King'ori
@uli-fischer I built this recently: docker.io/syck0/flannel:v0.21.5-hostprocess. It works for me. Try it out
@glerb which image in particular were you trying to pull?
@zwpaper there's this PR #2587 as well to enable `nerdctl build` for windows
@TBBle do you have some free cycles to complete this? [buildkit v0.13.0-rc2](https://github.com/moby/buildkit/releases/tag/v0.13.0-rc2) includes the windows buildkitd binary and would be great to have nerdctl working as well. Happy to pick...
> Okay, I've rebased it, and we'll let CI confirm I didn't break anything. I am not currently in a position to test it locally tonight though. I should have...
I got `nerdctl build` to run but with a couple of problems: **1.Nerdctl sets a default windows path on container images:** ```set PATH Path=c:\Windows\System32;c:\Windows ``` This is a universal problem...
Sounds good to me
This bug is caused by a containerd bug [here](https://github.com/containerd/containerd/blob/d015c99b2ec990c914a4b4546ec10d61cd947ab0/oci/spec_opts.go#L193C58-L193C72`) which only has default for unix env: ```go func WithDefaultPathEnv(_ context.Context, _ Client, _ *containers.Container, s *Spec) error { s.Process.Env =...
The fix for this was backported into Containerd 1.7.11 and 1.6.26. I've confirmed the bug no longer repros on the latest release of nerdctl
@iancward please provide some additional context on the specific scenario you are solving and an approach to test this.