Jaeger invalid mount error BB 1.8.0 and v1.20.7+rke2r2
Bug
Description
The jaeger
pod in the jaeger
namespace fails to start on RKE2 v1.20.7+rke2r2
with the following error:
Warning Failed 48m kubelet Error: failed to create containerd task: OCI runtime create failed: invalid mount {Destination:[/tmp] Type:bind Source:/var/lib/rancher/rke2/agent/containerd/io.containerd.grpc.v1.cri/containers/jaeger/volumes/c89ab49b2b75c2fbf36f5665187b74c7eca388a7cb5fbb6e2ceea54aeb65da5f Options:[rbind rprivate rw]}: mount destination [/tmp] not absolute: unknown
Warning Failed 48m kubelet Error: failed to create containerd task: OCI runtime create failed: invalid mount {Destination:[/tmp] Type:bind Source:/var/lib/rancher/rke2/agent/containerd/io.containerd.grpc.v1.cri/containers/jaeger/volumes/50cb03fd93c7ad679494a179200318ba2a12df501f7cb4b4eaede662726a6fed Options:[rbind rprivate rw]}: mount destination [/tmp] not absolute: unknown
Downgrading to RKE2 v1.20.6+rke2r1
results in the pod starting without issue.
This update to runc might be the culprit as it was introduced in RKE2 v1.20.7+rke2r1
:
https://github.com/opencontainers/runc/security/advisories/GHSA-c3xm-pvg7-gh7r.
BigBang Version
1.8.0