![]() The `cri-in-userns` stage is for testing "CRI-in-UserNS", which should be used in conjunction with "Kubelet-in-UserNS": https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2033-kubelet-in-userns-aka-rootless This feature is mostly expected to be used for `kind` and `minikube`. Requires Rootless Docker/Podman/nerdctl with cgroup v2 delegation: https://rootlesscontaine.rs/getting-started/common/cgroup2/ (Rootless Docker/Podman/nerdctl prepares the UserNS, so we do not need to create UserNS by ourselves) Usage: ``` podman build --target cri-in-userns -t cri-in-userns -f contrib/Dockerfile.test . podman run -it --rm --privileged cri-in-userns ``` The stage is tested on CI with Rootless Podman on Fedora 34 on Vagrant. Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp> |
||
---|---|---|
.. | ||
ansible | ||
apparmor | ||
autocomplete | ||
aws | ||
Dockerfile.test.d/cri-in-userns | ||
fuzz | ||
gce | ||
linuxkit | ||
nvidia | ||
seccomp | ||
snapshotservice | ||
Dockerfile.test | ||
README.md |
contrib
The contrib
directory contains packages that do not belong in the core containerd packages but still contribute to overall containerd usability.
Package such as Apparmor or Selinux are placed in contrib
because they are platform dependent and often require higher level tools and profiles to work.
Packaging and other built tools can be added to contrib
to aid in packaging containerd for various distributions.
Testing
Code in the contrib
directory may or may not have been tested in the normal test pipeline for core components.