Release Notes and Known Issues
Highlighted features and identified problems in CodeReady Containers 1.31
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Part I. Release notes
This section documents the most important features and bug fixes in the CodeReady Containers 1.31 product.
Chapter 1. Component versions
CodeReady Containers 1.31 is shipped with the following versions of the main components:
Table 1.1. CodeReady Containers, Component versions
OpenShift Container Platform
OpenShift client binary (
Chapter 2. Minimum system requirements
CodeReady Containers has the following minimum hardware and operating system requirements.
2.1. Hardware requirements
CodeReady Containers requires the following system resources:
- 4 physical CPU cores
- 9 GB of free memory
- 35 GB of storage space
The OpenShift cluster requires these minimum resources to run in the CodeReady Containers virtual machine. Some workloads may require more resources. To assign more resources to the CodeReady Containers virtual machine, see Configuring the virtual machine.
2.2. Operating system requirements
CodeReady Containers requires the following minimum version of a supported operating system:
2.2.1. Microsoft Windows
- On Microsoft Windows, CodeReady Containers requires the Windows 10 Fall Creators Update (version 1709) or newer. CodeReady Containers does not work on earlier versions of Microsoft Windows. Microsoft Windows 10 Home Edition is not supported.
- On macOS, CodeReady Containers requires macOS 10.14 Mojave or newer. CodeReady Containers does not work on earlier versions of macOS.
- On Linux, CodeReady Containers is only supported on Red Hat Enterprise Linux/CentOS 7.5 or newer (including 8.x versions) and on the latest two stable Fedora releases.
- When using Red Hat Enterprise Linux, the machine running CodeReady Containers must be registered with the Red Hat Customer Portal.
- Ubuntu 18.04 LTS or newer and Debian 10 or newer are not officially supported and may require manual set up of the host machine.
- See Required software packages to install the required packages for your Linux distribution.
Chapter 3. Changes and improvements
This section highlights some of the notable changes introduced in CodeReady Containers 1.31.
3.1. New features
CodeReady Containers brings a minimal, preconfigured OpenShift Container Platform 4 cluster to your local laptop or desktop computer for development and testing purposes. CodeReady Containers is delivered as a Red Hat Enterprise Linux virtual machine that supports native hypervisors for Linux, macOS, and Microsoft Windows 10.
- CodeReady Containers is designed for local development and testing on an OpenShift 4 cluster. To run an OpenShift 3 cluster locally, see Red Hat Container Development Kit.
3.1.1. Technology Previews
Support for these features falls under the Technology Preview Features Support Scope.
CodeReady Containers 1.31 includes the ability to create a custom bundle based on the currently running cluster with the
crc bundle generatecommand. This command, its parameters, and behavior may change in incompatible ways in future releases.
3.2. Notable changes
- CodeReady Containers 1.31 provides OpenShift Container Platform 4.8.4 as the embedded OpenShift version.
On Linux, CodeReady Containers now uses
systemdsocket activation to start the CodeReady Containers daemon when needed.
Part II. Known issues
This section describes issues that users of CodeReady Containers 1.31 may encounter, as well as possible workarounds for these issues.
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
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
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
$ crc start -n 184.108.40.206
Chapter 5. Issues on macOS
This section describes CodeReady Containers issues that affect users on a macOS host.
5.1. Hibernation causes VM time to desynchronize
Time in the CodeReady Containers virtual machine can become desynchronized with the time on your host machine. This issue occurs if the CodeReady Containers virtual machine is running when the host machine enters hibernation. To resolve this issue, stop the CodeReady Containers virtual machine and restart it:
$ crc stop $ crc start
Chapter 6. Issues on Microsoft Windows
This section describes CodeReady Containers issues that affect users on a Microsoft Windows host.
crc setup command must be run following installation with the MSI installer
After installing CodeReady Containers with the MSI installer and rebooting your computer, ensure you run the
crc setup command in Command Prompt or PowerShell to complete the installation.
crc cleanup command may fail with a permission error
crc setup followed by
crc cleanup without restarting your host machine between commands will cause
crc cleanup to report the following error:
Post "http://unix/clean": open \\.\pipe\crc-admin-helper: Access is denied.
To complete the
crc cleanup command, restart your host machine and run the command again.
6.3. Unexpected behavior when run outside of
The Hyper-V driver will fail when the
crc binary is executed from a network drive. The
crc binary must be placed in a location on
%WINDRIVE% is normally set to
6.4. CodeReady Containers expects
FullLanguage support in PowerShell
ConstrainedLanguage PowerShell mode is supported with exceptions determined by your system administrator.
crc oc-env command does not work with special characters in
On Microsoft Windows, PowerShell and Command Prompt do not use the UTF-8 encoding. As a result, running the
crc oc-env command with special characters present in the
%PATH% will not accurately encode UTF-8 characters. There is no known workaround for this issue.
- See the Red Hat CodeReady Containers Getting Started Guide for an overview of CodeReady Containers features and an introduction to the use of OpenShift Container Platform.
Report issues with CodeReady Containers or request new features using the OpenShift Container Platform product with the
crccomponent on Red Hat BugZilla.