Closed mqasimsarfraz closed 1 year ago
Which version of cri-o/runc did you use? Was it compiled with a sufficiently recent version of github.com/opencontainers/runtime-spec?
docker run --rm -it --entrypoint=/usr/lib/cri-o-runc/sbin/runc ghcr.io/mqasimsarfraz/kickbase:v0.0.37-1675280603-15763 --version
runc version v1.0.1
spec: 1.0.2-dev
go: go1.13.8
libseccomp: 2.5.1
You are right, it seems old. Now I remember cri-o
uses custom runc in minikube
(driver=docker). After switching to updated runc version I was able to test changes on cri-o as well.
This PR use
oci-annotations
package to get pod context form container runtime annotations. The changes itself are simple butvendor
changes are making them blotted. Please let me know if you have any feedback on that.Testing done
You can see from the logs that pod context is being resolved via annotations. Also,
containerd
namespace annotation will be used as well.Logs
before
after
crio
Works fine on crio as well: