Chapter 2. Known issues

Issues that users of Red Hat OpenShift Local 2.22 might have, as well as possible workarounds for these issues.

2.1. General issues

Issues affecting all supported platforms.

2.1.1. 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.

2.1.2. 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.

You cannot disable Monitoring after enabling these features.

Workaround

To disable monitoring again:

  1. Delete the virtual machine:

    $ crc delete
  2. Create a virtual machine:

    $ crc start

2.1.3. 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

2.1.4. 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 nameserver when starting the Red Hat OpenShift Local virtual machine by using the -n flag:

    $ crc start -n 8.8.8.8

2.1.5. Running crc setup might give you a known error

When you run the crc setup command, you might get the following error:

unable to get verified hash for default bundle: Get "https://developers.redhat.com/content-gateway/file/pub/openshift-v4/clients/crc/bundles/openshift/4.12.13/sha256sum.txt.sig": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Workaround

  • Try running the crc setup command till the error is resolved.

2.2. Issues on Microsoft Windows

This section describes Red Hat OpenShift Local issues that affect users on a Microsoft Windows host.

2.2.1. Completing the installation after installation with the Microsoft Standard Installer (MSI)

Procedure

  1. Install Red Hat OpenShift Local with the MSI installer
  2. Reboot your computer
  3. Run the command in Command Prompt or PowerShell:

    $ crc setup

2.2.2. The crc cleanup command might fail with a permission error

Running crc setup followed by crc cleanup without restarting your host computer between commands will cause crc cleanup to report the following error:

Post "http://unix/clean": open \\.\pipe\crc-admin-helper: Access is denied.

Workaround

  1. Reboot your computer
  2. Run the command:

    $ crc cleanup

2.2.3. Unexpected behavior when run outside %WINDRIVE%

The Hyper-V driver will fail when you start the crc binary from a network drive.

Workaround

  • Move the crc binary to a location on %WINDRIVE%.

    %WINDRIVE% is usually set to C:\.

2.2.4. Red Hat OpenShift Local expects FullLanguage support in PowerShell

Red Hat OpenShift Local supports the ConstrainedLanguage PowerShell mode with exceptions determined by your system administrator.

2.2.5. The crc oc-env command does not work with special characters in %PATH%

On Microsoft Windows, PowerShell and Command Prompt do not use the UTF-8 encoding. Therefore, running the crc oc-env command with special characters present in the %PATH% will not accurately encode UTF-8 characters.

Workaround

  • Move the crc binary to a location containing no special characters.

Additional resources

2.3. Issues on macOS

This section describes Red Hat OpenShift Local issues that affect users on a macOS host.

2.3.1. Hibernation causes VM time to desynchronize

Time in the Red Hat OpenShift Local virtual machine can become desynchronized with the time on your host. This issue occurs if the Red Hat OpenShift Local virtual machine is running when the host machine enters hibernation.

Workaround

  1. Stop the Red Hat OpenShift Local virtual machine:

    $ crc stop
  2. Restart the Red Hat OpenShift Local virtual machine:

    $ crc start