Kubernetes use of opencontainers/runc as a library is placing undue burden on the runc team, for example:
We now have a cgroups specific library in containerd org that we can explore to start slowly replacing functionality we needed earlier from runc i think.
https://github.com/containerd/cgroups
As of right now k/k master shows the following imports of opencontainers/runc:
❯ rg '"github.com/opencontainers/runc' | grep -v vendor | cut -f 2 -d '"' | sort | uniq -c | sort
1 github.com/opencontainers/runc/libcontainer/cgroups/systemd
1 github.com/opencontainers/runc/libcontainer/utils
2 github.com/opencontainers/runc/libcontainer/apparmor
2 github.com/opencontainers/runc/libcontainer/cgroups/manager
2 github.com/opencontainers/runc/libcontainer/configs
2 github.com/opencontainers/runc/libcontainer/userns
3 github.com/opencontainers/runc/libcontainer/cgroups/fscommon
17 github.com/opencontainers/runc/libcontainer/cgroups
/sig node
Kubernetes use of
opencontainers/runcas a library is placing undue burden on the runc team, for example:internalopencontainers/runc#3028We now have a cgroups specific library in containerd org that we can explore to start slowly replacing functionality we needed earlier from runc i think.
https://github.com/containerd/cgroups
As of right now k/k master shows the following imports of opencontainers/runc:
/sig node