debug: start cri-docker before starting minikube cluster

Signed-off-by: Höhl, Lukas <lukas.hoehl@accso.de>
This commit is contained in:
Höhl, Lukas 2022-06-28 12:01:38 +02:00
parent d391b28d62
commit 8923941358
1 changed files with 4 additions and 1 deletions

View File

@ -54,6 +54,9 @@ sudo cp /tmp/cri-dockerd/packaging/systemd/* /etc/systemd/system
sudo systemctl daemon-reload
sudo systemctl enable cri-docker.service
sudo systemctl enable --now cri-docker.socket
sudo systemctl start cri-docker.socket
sudo systemctl start cri-docker.service || systemctl status cri-docker.service
sudo systemctl status cri-docker
CRICTL_VERSION="v1.17.0"
curl -L https://github.com/kubernetes-sigs/cri-tools/releases/download/$CRICTL_VERSION/crictl-${CRICTL_VERSION}-linux-amd64.tar.gz --output crictl-${CRICTL_VERSION}-linux-amd64.tar.gz
@ -66,7 +69,7 @@ cat /proc/cpuinfo
# need to run minikube start as root since user doesn't have permissions to communicate with docker in minikube 1.26
# See https://minikube.sigs.k8s.io/docs/drivers/none/#other
sudo minikube start --vm-driver=none --force || sudo minikube logs;
sudo minikube start --vm-driver=none --force || sudo minikube logs && ;
minikube status
minikube addons enable registry
kubectl cluster-info