- Posted In
- CodeReady Containers
Few issues I am continuously facing are
1] Never able to successfully execute crc start. Most of the time, it never succeeds at
"Waiting for kube-apiserver availability... [takes around 2min]"
when run in debug mode I get following mesages
level=debug msg="retry loop: attempt 9"
level=debug msg="Running SSH command: timeout 5s oc get nodes --context admin --cluster crc --kubeconfig /opt/kubeconfig"
level=debug msg="SSH command results: err: Process exited with status 1, output: "
level=debug msg="The connection to the server api.crc.testing:6443 was refused - did you specify the right host or port?\n"
level=debug msg="error: Temporary error: ssh command error:\ncommand : timeout 5s oc get nodes --context admin --cluster crc --kubeconfig /opt/kubeconfig\nerr : Process exited with status 1\n - sleeping 1s"
Any mechanism to increase timeout in "timeout 5s oc get nodes --context admin --cluster crc --kubeconfig /opt/kubeconfig"?
when executed separately (without timeout) "oc get nodes" command works fine and output is
crc-pkjt4-master-0 Ready master,worker 18d v1.20.0+df9c838
2] Well even then crc is up and I am able to login but build never succeeds.
In fact, I am able login to host api.crc.testing using command
ssh -i ~/.crc/machines/crc/id_ecdsa email@example.com
and able to successfully resolve github.com from the shell. Check below output on command line of 192.168.130.11
github.com has address 220.127.116.11
github.com mail is handled by 1 aspmx.l.google.com.
github.com mail is handled by 5 alt1.aspmx.l.google.com.
github.com mail is handled by 5 alt2.aspmx.l.google.com.
github.com mail is handled by 10 alt3.aspmx.l.google.com.
github.com mail is handled by 10 alt4.aspmx.l.google.com.
BUT, then why build fails with error =>
Cloning "https://github.com/jboss-openshift/openshift-quickstarts" ...
error: fatal: unable to access 'https://github.com/jboss-openshift/openshift-quickstarts/': Could not resolve host: github.com