cri-dockerd does not set Resources to ContainerStatus

[esotsal]

cri-dockerd does not set Resources to ContainerStatus code

For comparison containerd sets it code

This results to K8s failure to throttle pod so that it follows resized CPU limit on minikube when cri-dockerd is used.

InPlacePodVerticalScaling in K8s is soon going to reach Beta and luck of such support from cri-dockerd means that end users will face this limitation as described kubernetes/kubernetes#118371 in minikube if cri-dockerd is used.