Red Hat CodeReady Containers (CRC) is the former name of Red Hat OpenShift Local: a minimal, preconfigured OpenShift cluster that runs on a developer’s computer for local application development and testing. It is useful when you need an OpenShift environment without provisioning separate server infrastructure, but it is not a production deployment.
What CodeReady Containers is—and what it is called now
Red Hat renamed CodeReady Containers to OpenShift Local in May 2022, alongside the OpenShift Local 2.0 release. Red Hat’s current overview identifies it as “Red Hat OpenShift Local (formerly Red Hat CodeReady Containers)” and describes its purpose as local development and testing on an OpenShift cluster.
The change matters when following older tutorials: references to CRC or CodeReady Containers may describe the predecessor name for the same local-development offering. The name change alone does not mean that every command, download, platform option, or requirement in an old guide remains current.
What developers use OpenShift Local for
OpenShift Local provides a small, preconfigured cluster on a local computer so developers can build and test container-based applications in an environment that emulates aspects of cloud development. The applications run in containers hosted by Kubernetes. Its value is convenience: you can work against a local OpenShift cluster rather than first arranging server infrastructure.
That scope is narrower than a full production or shared team deployment. The goal is a laptop-oriented development and testing environment, not a substitute for planning, sizing, securing, and operating a supported production OpenShift cluster. Older setup examples also show that local clusters may have a reduced feature set to conserve resources: a 2020 Red Hat tutorial, for instance, describes several operators being disabled in the setup it covers.
Historical system requirements: figures from 2019, not current guidance
Red Hat’s September 5, 2019 introduction listed the following minimums for the CodeReady Containers environment documented at that time. It also said a native host hypervisor was required.
Rank #2
| Item | Historical figure | Qualification |
|---|---|---|
| Virtual CPUs | 4 vCPUs | Minimum listed by Red Hat in 2019 for the then-current environment. |
| Memory | 8 GB | Minimum listed by Red Hat in 2019 for the then-current environment. |
| Storage | 35 GB | Minimum listed by Red Hat in 2019 for the then-current environment. |
These are historical specifications, not verified requirements for current OpenShift Local releases. Check Red Hat’s current installation guidance for supported operating systems, hypervisors, and resource needs before installing or deciding whether a computer is suitable; the 2019 figures should not be used as a current compatibility guarantee.
Workload needs can also exceed a basic cluster’s requirements. A separate Red Hat article from April 6, 2022 gives an example AI/ML configuration of 8 CPUs, 20,000 MB of memory, and 70 GB of disk. That is a workload-specific example, not a general minimum or a present-day recommendation.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
How the older CRC setup flow worked
Red Hat’s 2019 walkthrough documents the historical workflow below. Treat it as context for old instructions, not as current installation steps; download locations, prerequisites, platform support, and account or entitlement requirements may have changed.
- Extract the downloaded archive and make the
crccommand available on yourPATH. - Run
crc setupto prepare the local environment. - Run
crc startto start the cluster. The 2019 walkthrough says users were prompted for a Red Hat pull secret and needed a Red Hat account to access it.
For a new installation, follow the current OpenShift Local product information and its linked installation documentation rather than relying on an archived CodeReady Containers walkthrough.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.CRC community binaries and Red Hat VM images are not interchangeable terms
CRC can also refer to a community project and its binaries, while OpenShift Local is Red Hat’s product branding. This distinction matters in some workflows involving virtual-machine images. A March 27, 2025 Red Hat article says that the Red Hat OpenShift or Red Hat build of MicroShift VM images in the presets it discusses require valid product subscriptions; it also describes an OKD preset as an option without a Red Hat product subscription.
That statement concerns the builds and presets in that article, not every CRC binary, OpenShift Local use, or possible entitlement scenario. Subscription rules can change, so verify the current terms for the specific image and product you intend to run. See Red Hat’s 2025 article on MicroShift with OpenShift Local and Podman Desktop for the context of its examples.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Best Value
How to read older CodeReady Containers guides
- Translate the name, not the instructions automatically: CodeReady Containers became OpenShift Local in 2022, but an old command or download link may no longer apply.
- Date-check hardware numbers: the frequently repeated 4-vCPU, 8-GB-memory, and 35-GB-storage figures come from a 2019 article.
- Keep the use case local: CRC/OpenShift Local is intended for development and testing, not production operations.
- Check the image’s entitlement terms: community binaries and Red Hat-branded VM images can have different subscription considerations.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
