CRC Start on Windows 10 Pro Failed: timeout 5s oc get nodes --context admin --cluster crc --kubeconfig /opt/kubeconfig err : Process exited with status 124

Posted on

Hello
I am trying to install CRC-4.11.1 on Windows 10 Pro
Host : Core i3-4150, RAM 16GB, Windows 10 Pro
Hypervisor: Hyper-V
bundle : crc_hyperv_4.11.1_amd64.crcbundle
CRC Version :
crc version : 2.8.0+ff5e73ea
Openshift version: 4.11.1
Podman version : 4.1.1
V Switch : crc hyper-v switch, default hyper-v switch

Host network is local network, so i downloaded crc_hyperv_4.11.1_amd64.crcbundle and crc-windows-amd64.tar.xz
And i created Microsoft KM-TEST loopback Network Adapter, and generate CRC Hyper-V v-Switch based on the km-test loopback adapter, and i shared Ethernet 2(host adapter) and crc v-switch
And then i started to install OpenShift Local
crc setup -b ~/Download/crc_hyperv_4.11.1_amd64.crcbundle
crc start -p ~/Download/pull-secret.txt
but i failed
Outputs is following
...
api.crc.testing resolved to [127.0.0.1]
CRC instance is running with IP 127.0.0.1"
...
Temporary error: ssh command error:
command : timeout 5s oc get nodes --context admin --cluster crc --kubeconfig /opt/kubeconfig
err : Process exited with status 124

In my opinion, crc instance has 127.0.0.1, so ssh command failed
C:\Windows\system32\drivers\etc\hosts file' contents is
127.0.0.1 api.crc.testing canary-openshift-ingress-canary.apps-crc.testing console-openshift-console.apps-crc.testing default-route-openshift-image-registry.apps-crc.testing downloads-openshift-console.apps-crc.testing oauth-openshift.apps-crc.testing

Also i found that there is no hyper-v v switch adding step
How to do for fixing this.

Attachments

bb

Responses