Description of problem:

The master-restart shim is using docker commands directly.  This does not work when the control plane nodes are running cri-o.   Do we intend these commands for customer consumption?   I see TODOs in the scripts for cri-o but they are currently not implemented.


Version-Release number of selected component (if applicable):  3.10.0-0.32.0


How reproducible: Always


Steps to Reproduce:
1. On a cluster using cri-o as the container run time, master-restart api


Actual results:

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?


Expected results:

Master api restarts