Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save tnk4on/318a748c7ce6ca4672a9159a57f3fef1 to your computer and use it in GitHub Desktop.
Save tnk4on/318a748c7ce6ca4672a9159a57f3fef1 to your computer and use it in GitHub Desktop.
If the host running the CRC has complex name resolution settings, you can start the CRC by specifying a nameserver.
$ crc start -n 192.168.1.1
INFO Checking if oc binary is cached
INFO Checking if podman remote binary is cached
INFO Checking if goodhosts binary is cached
INFO Checking minimum RAM requirements
INFO Checking if running as non-root
INFO Checking if HyperKit is installed
INFO Checking if crc-driver-hyperkit is installed
INFO Checking file permissions for /etc/hosts
INFO Checking file permissions for /etc/resolver/testing
INFO Starting CodeReady Containers VM for OpenShift 4.5.9...
INFO CodeReady Containers VM is running
INFO Starting network time synchronization in CodeReady Containers VM
INFO Verifying validity of the cluster certificates ...
INFO Adding 192.168.1.1 as nameserver to the instance ...
INFO Network restart not needed
INFO Check internal and public DNS query ...
INFO Check DNS query from host ...
INFO Starting OpenShift kubelet service
INFO Starting OpenShift cluster ... [waiting 3m]
INFO Updating kubeconfig
WARN The cluster might report a degraded or error state. This is expected since several operators have been disabled to lower the resource usage. For more information, please consult the documentation
Started the OpenShift cluster
To access the cluster, first set up your environment by following 'crc oc-env' instructions.
Then you can access it by running 'oc login -u developer -p developer https://api.crc.testing:6443'.
To login as an admin, run 'oc login -u kubeadmin -p duduw-yPT9Z-hsUpq-f3pre https://api.crc.testing:6443'.
To access the cluster, first set up your environment by following 'crc oc-env' instructions.
You can now run 'crc console' and use these credentials to access the OpenShift web console.
@tnk4on
Copy link
Author

tnk4on commented Sep 21, 2020

"/etc/resolv.conf" in the CRC VM after starting the CRC with the name server.

[core@crc-zqfk6-master-0 ~]$ cat /etc/resolv.conf
# Generated by CRC
search crc.testing
nameserver 10.88.0.8
nameserver 192.168.64.1
nameserver fe80::4d4:cf54:e5a9:f5a1%enp0s1
nameserver 192.168.1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment