jaegertracing
[Bug]: not support crun + containerd
What happened?
using containerd + crun running operator
Steps to reproduce
install containerd + crun
kubectl logs -f -n observability jaeger-operator-cc7d8bd9c-b9d4w
exit status 2
Expected behavior
running operator in crun and containerd runtime
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
Hi! Thanks for reporting. Can you provide more information? Would you like yo send a PR?
When I use crun to run the cluster, the operator cannot run normally and even the log cannot be queried. containerd version : 1.7.18 crun version 1.15
but , use runc. It runs normally, but it doesn't work when using crun. Is there any limitation in the code that causes this problem? Or is it causing a crun bug?
I don't think there should be anything related to the code.
Can you try to build the container image in your environment and run it in your cluster?
I don't think there should be anything related to the code.
Can you try to build the container image in your environment and run it in your cluster?
There should be no problem with the docker image . In the same environment, I can switch runc to run normally. Is it related to relying on underlying libraries such as cgroup?