Skip to content
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

Need help to understand non-linux (Windows) branch in go-runc #94

Open
ningziwen opened this issue Dec 30, 2022 · 3 comments
Open

Need help to understand non-linux (Windows) branch in go-runc #94

ningziwen opened this issue Dec 30, 2022 · 3 comments

Comments

@ningziwen
Copy link

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?

@kzys
Copy link
Member

kzys commented Jan 13, 2023

Seems it was for hcsshim.

cc @jterry75 because of #45

@jterry75
Copy link
Contributor

Lolz its march and I have now seen this. Still need help?

@jterry75
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants