-
Notifications
You must be signed in to change notification settings - Fork 53
Consideration: moving selinux library out of runc into a new project #27
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
Comments
LGTM |
👍 for what it's worth I've already created the project at https://github.com/runcom/go-selinux to have a look at how it would look like. |
go-selinux is fine with me. |
Can you give me a list of maintainers for the project? @rhatdan @runcom and who else? @crosbymichael ? Thanks |
Also FYI @opencontainers/runc-maintainers |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's been a discussion in the OCI TDC about potentially moving the selinux library out of runc and into a new project (say something like opencontainers/libselinux)
I'm creating this issue as a placeholder while the OCI TDC finishes debating whether to move forward or not. If we move forward, we will consult the TOB and begin a formal project proposal.
cc: @mrunalp
The text was updated successfully, but these errors were encountered: