Chapter 4. General issues
Issues affecting all supported platforms.
4.1. Increased startup time for the OpenShift Container Platform 4.7 cluster
Due to an upstream issue, the cluster embedded in CodeReady Containers will take longer than usual to start using the crc start command.
For more information about the issue, see BZ#1927263: kubelet service takes around 43 secs to start container when started from stopped state.
4.2. Metrics are disabled by default
To ensure CodeReady Containers 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 CodeReady Containers virtual machine uses by default.
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 CodeReady Containers 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 CodeReady Containers virtual machine by default. Enabling multiple Operators may increase memory requirements.
See Configuring the virtual machine in the Red Hat CodeReady Containers Getting Started Guide to assign additional memory.
4.4. CodeReady Containers does not work when the first nameserver is IPv6
DNS resolution to the CodeReady Containers virtual machine can be disrupted if the first nameserver is IPv6.
To work around this issue, specify an IPv4 nameserver when starting the CodeReady Containers virtual machine using the -n flag:
$ crc start -n 8.8.8.8
