-
Language:
English
-
Language:
English
Release Notes and Known Issues
Highlighted features and identified problems in CodeReady Containers 1.16
Kevin Owen
kowen@redhat.com
devtools-docs@redhat.com
Abstract
Part I. Release notes
This section documents the most important features and bug fixes in the CodeReady Containers 1.16 product.
Chapter 1. Component versions
CodeReady Containers 1.16 is shipped with the following versions of the main components:
Table 1.1. CodeReady Containers, Component versions
Component | Version |
---|---|
OpenShift Container Platform | 4.5.9 |
OpenShift client binary ( | v4.5.9 |
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 virtual CPUs (vCPUs)
- 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.
2.2.2. macOS
- On macOS, CodeReady Containers requires macOS 10.12 Sierra or newer. CodeReady Containers does not work on earlier versions of macOS.
2.2.3. Linux
- 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.16.
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.
- CodeReady Containers now supports most editions of Microsoft Windows 10. Microsoft Windows 10 Home Edition is not supported.
3.1.1. Technology Previews
Support for these features falls under the Technology Preview Features Support Scope.
An experimental system tray is included in this release of CodeReady Containers for macOS and Microsoft Windows. To enable the system tray, run the
crc setup
command with the--enable-experimental-features
flag:$ crc setup --enable-experimental-features
On Microsoft Windows, a prompt will appear requiring you to enter your login credentials.
To start CodeReady Containers from the system tray, you must configure the
bundle
andpull-secret-file
properties:$ crc config set bundle ~/.crc/cache/crc_hyperkit_4.5.9.crcbundle $ crc config set pull-secret-file path-to-pull-secret-file
The pull secret file can be downloaded from the Pull Secret section of the Install on Laptop: Red Hat CodeReady Containers page on cloud.redhat.com.
To remove the system tray, run the
crc cleanup
command:$ crc cleanup
3.2. Notable changes
- CodeReady Containers 1.16 provides OpenShift Container Platform 4.5.9 as the embedded OpenShift version.
Part II. Known issues
This section describes issues that users of CodeReady Containers 1.16 may encounter, as well as possible workarounds for these issues.
Chapter 4. General issues
Issues affecting all supported platforms.
4.1. Embedded certificates expire after 30 days
Each released crc
binary includes an embedded system bundle that expires 30 days after the release due to certificates embedded in the OpenShift cluster.
The certificate renewal process is not working as intended as of the CodeReady Containers 1.10 release. Install new versions of CodeReady Containers as they become available to ensure your cluster remains operational. For more information about upgrading CodeReady Containers, see Upgrading CodeReady Containers in the Red Hat CodeReady Containers Getting Started Guide.
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.
4.3. Hang on startup with an AMD Ryzen 3000 series CPU
The CodeReady Containers virtual machine may hang on startup via the crc start
command due to a hardware bug.
To resolve this issue, install the latest BIOS update for your motherboard.
4.4. 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.
Chapter 5. Issues on macOS
This section describes CodeReady Containers issues that affect users on a macOS host.
5.1. The system tray does not start the virtual machine
The experimental macOS system tray cannot start the CodeReady Containers virtual machine. To work around this issue, start the CodeReady Containers virtual machine from the command line using the crc start
command:
$ crc start
For more information, see Starting the virtual machine in the Red Hat CodeReady Containers Getting Started Guide.
5.2. The crc cleanup
command aborts with an error
The crc cleanup
command on macOS returns an error and stops the cleanup process from proceeding.
To resolve this issue, run the following command:
$ launchctl stop crc.daemon
5.3. 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.
6.1. Unexpected behavior when run outside of %WINDRIVE%
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%
. %WINDRIVE%
is normally set to C:\
.
6.2. CodeReady Containers expects FullLanguage
support in PowerShell
The ConstrainedLanguage
PowerShell mode is supported with exceptions determined by your system administrator.
Additional resources
- 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
crc
component on Red Hat BugZilla.