Calico CNI installation fails with cridocker v0.3.12

Expected Behavior

Prior to v0.3.12 we were able to successfully install calico cni provider using the tigera operator to a baremetal kubeadm managed kubernetes cluster.

Actual Behavior

When updating our process to use cri-docker v0.3.12 we see bind errors during calico deployment.

Initially the tigera-operator fails to deploy.

 Normal   Pulled     15m                 kubelet            Successfully pulled image "<<redacted>>/tigera/operator:v1.32.3" in 21.153634784s (21.153662597s including waiting)
  Warning  Failed     13m (x12 over 15m)  kubelet            Error: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /var/lib/calico

After manually creating the folder /var/lib/calico on the controller node, the tigera operator pod deploys, but calico cni pods fail with

 Normal   Pulled     2m20s                 kubelet            Successfully pulled image "quay.io/calico/cni:v3.27.0" in 7.987855195s (7.988025596s including waiting)
  Warning  Failed     35s (x10 over 2m20s)  kubelet            Error: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /opt/cni/bin
  Normal   Pulled     35s (x9 over 2m20s)   kubelet            Container image "quay.io/calico/cni:v3.27.0" already present on machine

Steps to Reproduce the Problem

1. install and configure cri-docker
2. Deploy a kubernetes cluster (v1.25.5) on docker
3. deploy the tigera-operator (v1.23.3)

Specifications

• Version: kubernetes v1.25.5
• Platform: ubuntu
• Subsystem: cri-docker v0.3.12

Start by reproducing the deployment with cri-dockerd v0.3.12, Kubernetes v1.25.5, Ubuntu, and the Tigera operator, then investigate why the bind sources /var/lib/calico and /opt/cni/bin are absent. Done means the operator and Calico CNI pods deploy successfully without invalid bind-mount errors.