Menu Close
Settings Close

Language and Page Formatting Options

Chapter 4. General issues

Issues affecting all supported platforms.

4.1. Proxy settings are improperly applied to the Podman preset

Proxy settings configured 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.2. Metrics are disabled by default

To ensure Red Hat OpenShift Local can run on a typical laptop, some resource-heavy services are disabled by default. One of these services is Prometheus and all of the related monitoring, alerting, and telemetry functionality.

Enabling these features will require more resources than the Red Hat OpenShift Local virtual machine uses by default.

Note

Monitoring cannot be disabled after enabling these features. To disable monitoring again, delete the virtual machine with crc delete and recreate a new one with crc start.

See Starting Monitoring, Alerting, and Telemetry in the Red Hat OpenShift Local Getting Started Guide to enable monitoring.

4.3. Enabling multiple 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 multiple Operators may increase memory requirements.

See Configuring the virtual machine in the Red Hat OpenShift Local Getting Started Guide to assign additional memory.

4.4. Red Hat OpenShift Local does not work when the first nameserver is IPv6

DNS resolution to the Red Hat OpenShift Local virtual machine can be disrupted if the first nameserver is IPv6.

To work around this issue, specify an IPv4 nameserver when starting the Red Hat OpenShift Local virtual machine using the -n flag:

$ crc start -n 8.8.8.8