Chapter 4. General issues
Issues affecting all supported platforms.
4.1. SSH key mismatch error
The crc cleanup command does not remove the Red Hat OpenShift Local instance SSH key from the user SSH known hosts.
Therefore, when attempting to access the Red Hat OpenShift Local instance with a command such as podman-remote, you might receive this error message:
Error: failed to connect: ssh: handshake failed: knownhosts: key mismatch
Workaround
Remove the leftover SSH key from the SSH know hosts:
$ ssh-keygen -R $(crc ip)
Additional resources
4.2. Proxy settings are improperly applied to the Podman preset
Proxy settings configured by using the crc config set command are not used by the podman-remote binary embedded in Red Hat OpenShift Local when the Podman preset is in use.
4.3. Red Hat OpenShift Local disables metrics by default
To ensure Red Hat OpenShift Local can run on a typical notebook, Red Hat OpenShift Local disables some resource-heavy services, such as Prometheus and all the related monitoring, alerting, and telemetry functions. You can enable these features.
Procedure
- See Configuring the virtual machine to assign more resources
- See Starting Monitoring, Alerting, and Telemetry
You cannot disable Monitoring after enabling these features.
Workaround
To disable monitoring again:
Delete the virtual machine:
$ crc delete
Create a virtual machine:
$ crc start
4.4. Enabling many Operators requires more memory than the default
The crc start command assigns 9 GiB of memory to the Red Hat OpenShift Local virtual machine by default. Enabling many Operators might increase memory requirements.
Workaround
- See Configuring the virtual machine to assign additional memory.
4.5. Red Hat OpenShift Local does not work when the first nameserver is IPv6
DNS resolution to the Red Hat OpenShift Local virtual machine might fail if the first nameserver is IPv6.
Workaround
Specify an IPv4
nameserverwhen starting the Red Hat OpenShift Local virtual machine by using the-nflag:$ crc start -n 8.8.8.8