You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering what is the use case of having non-linux branch in go-runc. My understanding is go-runc is a wrapper for runc and runc is linux-specific. Windows container runtime has a separated repo hcsshim to be used by containerd. So why does go-runc need windows branch? Does go-runc/runc have the plan to support Windows container?
The text was updated successfully, but these errors were encountered:
Its just because the client is built into some generic containerd calls and so rather than forking all of those go files we just have it return unsupported for windows
Hi, I'm new to go-runc and trying to learn go-runc from reading the docs and source code.
I noticed there is code for non-linux (Windows) branch in multiple places.
https://github.com/containerd/go-runc/blob/main/command_other.go
https://github.com/containerd/go-runc/blob/main/io_windows.go
I'm wondering what is the use case of having non-linux branch in go-runc. My understanding is go-runc is a wrapper for runc and runc is linux-specific. Windows container runtime has a separated repo hcsshim to be used by containerd. So why does go-runc need windows branch? Does go-runc/runc have the plan to support Windows container?
The text was updated successfully, but these errors were encountered: