Resolve most issues by stopping the {prod} virtual machine, deleting it, and starting a new instance.
-
You set up the host machine via the
{bin} setup
command. For more information, see [setting-up-codeready-containers_{context}]. -
You started {prod} via the
{bin} start
command. For more information, see [starting-the-virtual-machine_{context}]. -
You are using the latest {prod} release. Using a version earlier than {prod} 1.2.0 may result in errors related to expired x509 certificates. For more information, see [troubleshooting-expired-certificates_{context}].
To troubleshoot {prod}, perform the following steps:
-
Stop the {prod} virtual machine:
$ {bin} stop
-
Delete the {prod} virtual machine:
$ {bin} delete
-
Start the {prod} virtual machine:
$ {bin} start
NoteThe cluster takes a minimum of four minutes to start the necessary containers and Operators before serving a request.
If your issue is not resolved by this procedure, perform the following steps:
-
Search open issues for the issue that you are encountering.
-
If no existing issue addresses the encountered issue, create an issue and attach the
~/.crc/crc.log
file to the created issue. The~/.crc/crc.log
file has detailed debugging and troubleshooting information which can help diagnose the problem that you are experiencing.