-
Language:
English
-
Language:
English
Release Notes and Known Issues
Highlighted features and identified problems in CodeReady Containers 1.9
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.9 product.
Chapter 1. Component versions
CodeReady Containers 1.9 is shipped with the following versions of the main components:
Table 1.1. CodeReady Containers, Component versions
Component | Version |
---|---|
OpenShift Container Platform | 4.3.10 |
OpenShift client binary ( | v4.5.0 |
Chapter 2. Changes and improvements
This section highlights some of the notable changes introduced in CodeReady Containers 1.9.
2.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.
2.1.1. Technology Previews
Support for these features falls under the Technology Preview Features Support Scope.
-
On Red Hat Enterprise Linux and macOS, CodeReady Containers 1.9 provides experimental support for using
podman
through thecrc podman-env
command. This command allows the embeddedpodman
binary to access the container runtime provided by the CodeReady Containers virtual machine. An experimental system tray is included in this release of CodeReady Containers for macOS. To enable the system tray, run the
crc setup
command with the--enable-experimental-features
flag:$ crc setup --enable-experimental-features
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.3.10.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
2.2. Notable changes
- CodeReady Containers 1.9 provides OpenShift Container Platform 4.3.10 as the embedded OpenShift version.
-
CodeReady Containers now includes the
crc cleanup
command. Thecrc cleanup
command removes an existing CodeReady Containers virtual machine and reverts DNS changes made by thecrc setup
command. On macOS, thecrc cleanup
command also removes the system tray.
Part II. Known issues
This section describes issues that users of CodeReady Containers 1.9 may encounter, as well as possible workarounds for these issues.
Chapter 3. General issues
Issues affecting all supported platforms.
3.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.
Certificate recovery is automatic, but will add approximately three minutes to the start time of the CodeReady Containers virtual machine.
3.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.
3.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.
3.4. Enabling multiple Operators requires more memory than the default
The crc start
command assigns 8 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 4. Issues on Microsoft Windows
This section describes CodeReady Containers issues that affect users on a Microsoft Windows host.
4.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:\
.
4.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.