{"id":49099,"date":"2026-06-23T05:43:19","date_gmt":"2026-06-23T05:43:19","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=49099"},"modified":"2026-06-23T05:45:10","modified_gmt":"2026-06-23T05:45:10","slug":"openshift-local-crc-command-lines-guide","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/openshift-local-crc-command-lines-guide\/","title":{"rendered":"Openshift Local: crc command lines guide with example"},"content":{"rendered":"\n

Most important daily commands<\/h2>\n\n\n\n
Flow<\/th>Commands<\/th><\/tr><\/thead>
First setup<\/td>crc version<\/code> \u2192 crc setup<\/code> \u2192 crc start -p ~\/Downloads\/pull-secret.txt<\/code><\/td><\/tr>
Start work<\/td>crc start<\/code> \u2192 crc status<\/code> \u2192 crc console<\/code><\/td><\/tr>
Use oc<\/code><\/td>eval \"$(crc oc-env)\"<\/code> \u2192 crc console --credentials<\/code> \u2192 oc login ...<\/code><\/td><\/tr>
Stop work<\/td>crc stop<\/code><\/td><\/tr>
Reset cluster<\/td>crc stop<\/code> \u2192 crc delete --force<\/code> \u2192 crc cleanup<\/code> \u2192 crc setup<\/code> \u2192 crc start -p ~\/Downloads\/pull-secret.txt<\/code><\/td><\/tr>
Change CPU\/RAM<\/td>crc stop<\/code> \u2192 crc delete<\/code> \u2192 crc config set cpus 6<\/code> \u2192 crc config set memory 14336<\/code> \u2192 crc start<\/code><\/td><\/tr>
Switch preset<\/td>crc delete<\/code> \u2192 crc config set preset okd<\/code> \u2192 crc setup<\/code> \u2192 crc start<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Command<\/th>Purpose<\/th>When to Use<\/th>Common Example<\/th>Expected Output \/ Result<\/th><\/tr><\/thead>
crc<\/code><\/td>Base CRC command<\/td>To see general CLI help or available commands<\/td>crc<\/code><\/td>Shows CRC help and available commands<\/td><\/tr>
crc help<\/code><\/td>Show help<\/td>When you need command syntax<\/td>crc help start<\/code><\/td>Displays help for the selected command<\/td><\/tr>
crc version<\/code><\/td>Show CRC and bundled OpenShift\/MicroShift versions<\/td>First command to run after installation or upgrade<\/td>crc version<\/code><\/td>Shows CRC version, OpenShift version, MicroShift version<\/td><\/tr>
crc setup<\/code><\/td>Prepare local virtualization and networking<\/td>First-time setup, after upgrade, or after cleanup<\/td>crc setup<\/code><\/td>Your system is correctly setup for using CRC.<\/code><\/td><\/tr>
crc setup --check-only<\/code><\/td>Validate setup only<\/td>To check prerequisites without changing the system<\/td>crc setup --check-only<\/code><\/td>Reports whether system is ready<\/td><\/tr>
crc start<\/code><\/td>Start CRC instance<\/td>Start local OpenShift \/ OKD \/ MicroShift<\/td>crc start -p ~\/Downloads\/pull-secret.txt<\/code><\/td>Starts cluster and prints console URL and credentials<\/td><\/tr>
crc start -p<\/code><\/td>Start with pull secret file<\/td>OpenShift preset startup<\/td>crc start -p ~\/Downloads\/pull-secret.txt<\/code><\/td>Starts OpenShift using pull secret<\/td><\/tr>
crc start --pull-secret-file<\/code><\/td>Long form of pull secret option<\/td>Same as -p<\/code><\/td>crc start --pull-secret-file ~\/Downloads\/pull-secret.txt<\/code><\/td>Starts OpenShift using pull secret<\/td><\/tr>
crc start -c<\/code><\/td>Start with custom CPU count<\/td>When default CPU is not enough<\/td>crc start -c 6<\/code><\/td>Starts CRC with 6 CPUs<\/td><\/tr>
crc start -m<\/code><\/td>Start with custom memory<\/td>For heavier demos, monitoring, operators<\/td>crc start -m 14336<\/code><\/td>Starts CRC with 14 GiB memory<\/td><\/tr>
crc start -d<\/code><\/td>Start with custom disk size<\/td>When more disk space is needed<\/td>crc start -d 80<\/code><\/td>Starts CRC with 80 GiB disk<\/td><\/tr>
crc status<\/code><\/td>Show CRC status<\/td>Check whether VM and cluster are running<\/td>crc status<\/code><\/td>Shows VM status, OpenShift status, RAM, disk, cache<\/td><\/tr>
crc status --watch<\/code><\/td>Watch status continuously<\/td>During startup or troubleshooting<\/td>crc status --watch<\/code><\/td>Continuously refreshes CRC resource\/status view<\/td><\/tr>
crc stop<\/code><\/td>Stop CRC instance<\/td>End daily work while keeping VM data<\/td>crc stop<\/code><\/td>Stopped the instance<\/code><\/td><\/tr>
crc stop --force<\/code><\/td>Force stop CRC<\/td>If normal stop hangs or fails<\/td>crc stop --force<\/code><\/td>Forcibly stopped the instance<\/code><\/td><\/tr>
crc delete<\/code><\/td>Delete CRC instance<\/td>Reset cluster, switch preset, reclaim disk<\/td>crc delete<\/code><\/td>Prompts for confirmation, then deletes instance<\/td><\/tr>
crc delete --force<\/code><\/td>Delete without prompt<\/td>Automation or forced cleanup<\/td>crc delete --force<\/code><\/td>Deletes instance without confirmation<\/td><\/tr>
crc delete --clear-cache<\/code><\/td>Delete instance and cache<\/td>Full cleanup including cached bundle<\/td>crc delete --clear-cache --force<\/code><\/td>Deletes VM and cached CRC files<\/td><\/tr>
crc cleanup<\/code><\/td>Undo host setup changes<\/td>After deleting CRC or fixing broken networking<\/td>crc cleanup<\/code><\/td>Cleanup finished<\/code><\/td><\/tr>
crc console<\/code><\/td>Open web console<\/td>Access OpenShift web UI<\/td>crc console<\/code><\/td>Opens console in browser<\/td><\/tr>
crc console --url<\/code><\/td>Print console URL<\/td>When you only need the URL<\/td>crc console --url<\/code><\/td>Prints console URL<\/td><\/tr>
crc console --credentials<\/code><\/td>Print login credentials<\/td>To log in with oc<\/code> or web console<\/td>crc console --credentials<\/code><\/td>Shows developer<\/code> and kubeadmin<\/code> login commands<\/td><\/tr>
crc dashboard<\/code><\/td>Alias for crc console<\/code><\/td>Same as console<\/td>crc dashboard<\/code><\/td>Opens OpenShift console<\/td><\/tr>
crc oc-env<\/code><\/td>Print shell config for embedded oc<\/code><\/td>To add CRC\u2019s oc<\/code> binary to PATH<\/td>crc oc-env<\/code><\/td>Prints export\/eval instructions<\/td><\/tr>
eval \"$(crc oc-env)\"<\/code><\/td>Apply oc<\/code> environment<\/td>Before running oc<\/code> commands<\/td>eval \"$(crc oc-env)\"<\/code><\/td>Current shell can use CRC\u2019s oc<\/code><\/td><\/tr>
crc generate-kubeconfig<\/code><\/td>Print kubeconfig<\/td>To use CRC cluster with oc<\/code>\/Kubernetes tools<\/td>crc generate-kubeconfig > crc-kubeconfig<\/code><\/td>Writes kubeconfig content<\/td><\/tr>
crc ip<\/code><\/td>Print CRC VM IP address<\/td>Networking\/debugging<\/td>crc ip<\/code><\/td>Prints VM IP, for example 192.168.130.11<\/code><\/td><\/tr>
crc podman-env<\/code><\/td>Print Podman remote environment<\/td>Legacy Podman access to CRC VM<\/td>crc podman-env<\/code><\/td>Prints Podman environment variables<\/td><\/tr>
crc podman-env --root<\/code><\/td>Rootful Podman environment<\/td>If rootful Podman socket is needed<\/td>crc podman-env --root<\/code><\/td>Prints rootful Podman environment<\/td><\/tr>
crc config<\/code><\/td>Config command group<\/td>View\/change CRC settings<\/td>crc config --help<\/code><\/td>Shows config subcommands<\/td><\/tr>
crc config view<\/code><\/td>Show changed config values<\/td>Review active custom settings<\/td>crc config view<\/code><\/td>Lists non-default config values<\/td><\/tr>
crc config view --show-secrets<\/code><\/td>Show config including secrets<\/td>Only when you intentionally need secret values<\/td>crc config view --show-secrets<\/code><\/td>Shows secret config values too<\/td><\/tr>
crc config get<\/code><\/td>Get one config value<\/td>Check a specific setting<\/td>crc config get memory<\/code><\/td>Shows configured value or default notice<\/td><\/tr>
crc config set<\/code><\/td>Set config value<\/td>Before setup\/start or before recreating instance<\/td>crc config set memory 14336<\/code><\/td>Saves config value<\/td><\/tr>
crc config unset<\/code><\/td>Remove config override<\/td>Return setting to default<\/td>crc config unset memory<\/code><\/td>Removes custom value<\/td><\/tr>
crc bundle<\/code><\/td>Bundle command group<\/td>Advanced bundle operations<\/td>crc bundle --help<\/code><\/td>Shows bundle help<\/td><\/tr>
crc bundle generate<\/code><\/td>Generate custom bundle<\/td>Advanced\/custom CRC bundle creation<\/td>crc bundle generate<\/code><\/td>Generates bundle from running instance<\/td><\/tr>
crc bundle generate --force-stop<\/code><\/td>Force stop during bundle generation<\/td>If bundle generation needs forced VM stop<\/td>crc bundle generate --force-stop<\/code><\/td>Stops VM as needed and generates bundle<\/td><\/tr>
crc daemon<\/code><\/td>Hidden\/internal daemon command<\/td>Debugging CRC internals only<\/td>crc daemon<\/code><\/td>Starts CRC daemon process<\/td><\/tr>
crc daemon --watchdog<\/code><\/td>Daemon watchdog mode<\/td>Internal\/debug only<\/td>crc daemon --watchdog<\/code><\/td>Runs daemon with watchdog behavior<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

<\/p>\n\n\n\n

Below is a CRC \/ OpenShift Local command-line tutorial based on the latest CRC docs and v2.61.0 source I found<\/strong>. I\u2019m being careful here: no invented flags, no old crc setup --pull-secret<\/code>, and no fake subcommands.<\/p>\n\n\n\n

As of June 23, 2026<\/strong>, the latest upstream CRC release I found is v2.61.0 \/ 2.61.0-4.21.14<\/strong>, with OpenShift 4.21.14<\/strong> and OKD 4.21.0-okd-scos.8<\/strong>. (GitHub<\/a>)
Your local help output also matches this generation because your bundle default shows crc_vfkit_4.21.14_arm64.crcbundle<\/code>.<\/p>\n\n\n\n

Common config keys summary<\/h3>\n\n\n\n
Config Key<\/th>Purpose<\/th>Example<\/th><\/tr><\/thead>
preset<\/code><\/td>Choose runtime: OpenShift, OKD, MicroShift<\/td>crc config set preset openshift<\/code><\/td><\/tr>
cpus<\/code><\/td>Set CPU count<\/td>crc config set cpus 6<\/code><\/td><\/tr>
memory<\/code><\/td>Set memory in MiB<\/td>crc config set memory 14336<\/code><\/td><\/tr>
disk-size<\/code><\/td>Set disk size in GiB<\/td>crc config set disk-size 80<\/code><\/td><\/tr>
pull-secret-file<\/code><\/td>Save pull secret path<\/td>crc config set pull-secret-file ~\/Downloads\/pull-secret.txt<\/code><\/td><\/tr>
nameserver<\/code><\/td>Set DNS resolver<\/td>crc config set nameserver 8.8.8.8<\/code><\/td><\/tr>
disable-update-check<\/code><\/td>Disable CRC update check<\/td>crc config set disable-update-check true<\/code><\/td><\/tr>
consent-telemetry<\/code><\/td>Enable\/disable telemetry<\/td>crc config set consent-telemetry no<\/code><\/td><\/tr>
developer-password<\/code><\/td>Set developer user password<\/td>crc config set developer-password developer<\/code><\/td><\/tr>
kubeadmin-password<\/code><\/td>Set kubeadmin password<\/td>crc config set kubeadmin-password 'StrongPassword'<\/code><\/td><\/tr>
http-proxy<\/code><\/td>Configure HTTP proxy<\/td>crc config set http-proxy http:\/\/proxy.example.com:8080<\/code><\/td><\/tr>
https-proxy<\/code><\/td>Configure HTTPS proxy<\/td>crc config set https-proxy http:\/\/proxy.example.com:8080<\/code><\/td><\/tr>
no-proxy<\/code><\/td>Configure proxy bypass list<\/td>crc config set no-proxy 127.0.0.1,localhost,.testing<\/code><\/td><\/tr>
proxy-ca-file<\/code><\/td>Configure proxy CA certificate<\/td>crc config set proxy-ca-file \/path\/to\/ca.crt<\/code><\/td><\/tr>
host-network-access<\/code><\/td>Allow CRC to access host services<\/td>crc config set host-network-access true<\/code><\/td><\/tr>
enable-cluster-monitoring<\/code><\/td>Enable OpenShift monitoring stack<\/td>crc config set enable-cluster-monitoring true<\/code><\/td><\/tr>
ingress-http-port<\/code><\/td>Change HTTP ingress port<\/td>crc config set ingress-http-port 8080<\/code><\/td><\/tr>
ingress-https-port<\/code><\/td>Change HTTPS ingress port<\/td>crc config set ingress-https-port 8443<\/code><\/td><\/tr>
enable-shared-dirs<\/code><\/td>Enable shared directories<\/td>crc config set enable-shared-dirs true<\/code><\/td><\/tr>
persistent-volume-size<\/code><\/td>Set default persistent volume size<\/td>crc config set persistent-volume-size 20g<\/code><\/td><\/tr>
modify-hosts-file<\/code><\/td>Let CRC modify hosts file<\/td>crc config set modify-hosts-file true<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

CRC is the CLI behind Red Hat OpenShift Local<\/strong>, which runs a local single-node OpenShift \/ OKD \/ MicroShift development instance. It is for local development and testing, not production. (crc.dev<\/a>)<\/p>\n\n\n\n

\n\n\n\n

1. Commands verified from CRC v2.61.0<\/h1>\n\n\n\n

The v2.61.0 source tree contains these top-level command files: cleanup<\/code>, console<\/code>, daemon<\/code>, delete<\/code>, generate-kubeconfig<\/code>, ip<\/code>, oc-env<\/code>, podman-env<\/code>, setup<\/code>, start<\/code>, status<\/code>, stop<\/code>, and version<\/code>, plus the config<\/code> and bundle<\/code> command groups. (GitHub<\/a>)<\/p>\n\n\n\n

The config<\/code> group contains exactly these subcommands in v2.61.0:<\/p>\n\n\n

crc config get<\/span>\ncrc config set<\/span>\ncrc config unset\ncrc config view\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
The bundle<\/code> group contains exactly this visible subcommand in v2.61.0:<\/p>\n\n\n
crc bundle generate\n<\/code><\/span><\/pre>\n\n\n
(GitHub<\/a>)<\/p>\n\n\n\n
So the full verified command list is:<\/p>\n\n\n
crc\ncrc help\ncrc version\ncrc setup\ncrc start\ncrc status\ncrc stop\ncrc delete<\/span>\ncrc cleanup\ncrc console<\/span>\ncrc dashboard\ncrc oc-env\ncrc generate-kubeconfig\ncrc ip\ncrc podman-env\ncrc config\ncrc config get<\/span>\ncrc config set<\/span>\ncrc config unset\ncrc config view\ncrc bundle\ncrc bundle generate\ncrc daemon\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
2. Golden CRC lifecycle flow<\/h1>\n\n\n\n
Use this as the normal flow:<\/p>\n\n\n
crc version\ncrc config view\ncrc setup\ncrc start -p ~\/Downloads\/<\/span>pull-secret.txt\ncrc status\ncrc oc-env\neval<\/span> \"$(crc oc-env)\"<\/span>\ncrc console<\/span> --credentials\noc login -u developer -p <developer-password> https:\/\/api.crc.testing:6443<\/span>\ncrc console<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
For daily use after first setup:<\/p>\n\n\n
crc start\ncrc status\ncrc console<\/span>\ncrc stop\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
For a clean reset:<\/p>\n\n\n
crc stop\ncrc delete<\/span>\ncrc cleanup\ncrc setup\ncrc start -p ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
3. Pull secret correction<\/h1>\n\n\n\n
Your earlier command failed because this is wrong in current CRC:<\/p>\n\n\n
crc setup --pull-secret ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Use one of these instead:<\/p>\n\n\n
crc start -p ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
or:<\/p>\n\n\n
crc start --pull-secret-file ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
You can also save it into config:<\/p>\n\n\n
crc config set<\/span> pull-secret-file ~\/Downloads\/pull-secret.txt\ncrc start\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4. Command reference and tutorial<\/h1>\n\n\n\n
4.1 crc version<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Use this first to confirm your CRC binary, embedded OpenShift version, and MicroShift version.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc version\n<\/code><\/span><\/pre>\n\n\n
Expected output shape<\/h3>\n\n\n
CRC<\/span> version<\/span>: 2.61<\/span>.0<\/span>+<commit<\/span>>\nOpenShift<\/span> version<\/span>: 4.21<\/span>.14<\/span>\nMicroShift<\/span> version<\/span>: <microshift-version<\/span>>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
JSON output<\/h3>\n\n\n
crc version -o json\n<\/code><\/span><\/pre>\n\n\n
Expected shape:<\/p>\n\n\n
{\n \"version\"<\/span>: \"2.61.0\"<\/span>,\n \"commit\"<\/span>: \"<commit>\"<\/span>,\n \"openshiftVersion\"<\/span>: \"4.21.14\"<\/span>,\n \"microshiftVersion\"<\/span>: \"<microshift-version>\"<\/span>\n}\n<\/code><\/span>Code language:<\/span> JSON \/ JSON with Comments<\/span> (<\/span>json<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4.2 crc setup<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Run once after installing CRC, after changing some host-level settings, or after upgrading CRC. It prepares local virtualization and networking infrastructure.<\/p>\n\n\n\n
The official docs say crc setup<\/code> sets up the host machine and creates ~\/.crc<\/code> if needed. (crc.dev<\/a>)<\/p>\n\n\n\n
Basic command<\/h3>\n\n\n
crc setup\n<\/code><\/span><\/pre>\n\n\n
Expected successful output<\/h3>\n\n\n
Your system is correctly setup for<\/span> using CRC.\nUse 'crc start'<\/span> to start the instance\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Useful flags<\/h3>\n\n\n\n
From your installed help and v2.61.0 source:<\/p>\n\n\n
crc setup --check-only\ncrc setup --show-progressbars\ncrc setup --enable-experimental-features\ncrc setup -b \/path\/to\/bundle.crcbundle\ncrc setup --bundle \/path\/to\/bundle.crcbundle\ncrc setup -o json\n<\/code><\/span><\/pre>\n\n\n
When to use each<\/h3>\n\n\n\n
Use crc setup<\/code> for normal setup.<\/p>\n\n\n\n
Use this to only validate prerequisites without changing your system:<\/p>\n\n\n
crc setup --check-only\n<\/code><\/span><\/pre>\n\n\n
Use this if you want visible progress bars for download\/extraction:<\/p>\n\n\n
crc setup --show-progressbars\n<\/code><\/span><\/pre>\n\n\n
Use -b<\/code> only when you intentionally want to use a specific local, HTTP(S), or Docker bundle URI. Your current help output shows the default bundle path under ~\/.crc\/cache<\/code>.<\/p>\n\n\n\n
Do not use<\/h3>\n\n\n
crc setup --pull-secret ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
That flag is not valid on setup<\/code>.<\/p>\n\n\n\n
\n\n\n\n
4.3 crc start<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Creates\/starts the CRC VM and starts the selected runtime: OpenShift, OKD, or MicroShift. The official docs describe crc start<\/code> as starting the CRC instance and configured container runtime. (crc.dev<\/a>)<\/p>\n\n\n\n
Basic OpenShift start<\/h3>\n\n\n
crc start -p ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
or:<\/p>\n\n\n
crc start --pull-secret-file ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Interactive start<\/h3>\n\n\n
crc start\n<\/code><\/span><\/pre>\n\n\n
If no pull secret is configured or supplied, CRC can ask for it during startup. The getting-started docs show crc start<\/code> as the command and explain that OpenShift startup asks for the pull secret. (crc.dev<\/a>)<\/p>\n\n\n\n
Start with custom resources<\/h3>\n\n\n
crc start -c 6<\/span> -m 14336<\/span> -d 80<\/span> -p ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Meaning:<\/p>\n\n\n
-c \/ --cpus       CPU cores\n-m \/ --memory     memory in MiB\n-d \/ --disk-size  disk size in GiB\n-p                pull secret file\n<\/code><\/span><\/pre>\n\n\n
The v2.61.0 source defines --cpus<\/code>, --memory<\/code>, --disk-size<\/code>, --nameserver<\/code>, --bundle<\/code>, --pull-secret-file<\/code>, and --disable-update-check<\/code> on crc start<\/code>. (GitHub<\/a>)<\/p>\n\n\n\n
Full practical examples<\/h3>\n\n\n\n
Start with specific DNS resolver:<\/p>\n\n\n
crc start -n 8.8<\/span>.8<\/span>.8<\/span> -p ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Start without checking for new CRC versions:<\/p>\n\n\n
crc start --disable-update-check -p ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Start using a specific bundle:<\/p>\n\n\n
crc start -b ~\/.crc\/<\/span>cache\/crc_vfkit_4.21<\/span>.14<\/span>_arm64.crcbundle -p ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected successful OpenShift output<\/h3>\n\n\n
Started the OpenShift cluster.\n\nThe server is accessible via web console at:\n  https:\/\/console-openshift-console.apps-crc.testing<\/span>\n\nLog in as<\/span> administrator:\n  Username: kubeadmin\n  Password: <generated-or<\/span>-configured-password>\n\nLog in as<\/span> user:\n  Username: developer\n  Password: <developer-password>\n\nUse<\/span> the<\/span> 'oc<\/span>' command<\/span> line<\/span> interface<\/span>:\n  $ eval<\/span> \"$(crc<\/span> oc<\/span>-env<\/span>)\"\n  $ oc<\/span> login<\/span> -u<\/span> developer<\/span> https<\/span>:\/\/api<\/span>.crc<\/span>.testing<\/span>:6443\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
JSON output<\/h3>\n\n\n
crc start -p ~\/Downloads\/<\/span>pull-secret.txt -o json\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected shape:<\/p>\n\n\n
{\n \"success\"<\/span>: true<\/span>,\n \"clusterConfig\"<\/span>: {\n  \"clusterType\"<\/span>: \"openshift\"<\/span>,\n  \"cacert\"<\/span>: \"<certificate>\"<\/span>,\n  \"webConsoleUrl\"<\/span>: \"https:\/\/console-openshift-console.apps-crc.testing\"<\/span>,\n  \"url\"<\/span>: \"https:\/\/api.crc.testing:6443\"<\/span>,\n  \"adminCredentials\"<\/span>: {\n   \"username\"<\/span>: \"kubeadmin\"<\/span>,\n   \"password\"<\/span>: \"<password>\"<\/span>\n  },\n  \"developerCredentials\"<\/span>: {\n   \"username\"<\/span>: \"developer\"<\/span>,\n   \"password\"<\/span>: \"<password>\"<\/span>\n  }\n }\n}\n<\/code><\/span>Code language:<\/span> JSON \/ JSON with Comments<\/span> (<\/span>json<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4.4 crc status<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Check VM status, OpenShift\/OKD\/MicroShift status, resource usage, cache usage, and cache directory.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc status\n<\/code><\/span><\/pre>\n\n\n
Expected output shape<\/h3>\n\n\n
CRC VM:          Running\nOpenShift:       Running (v4.21.14)\nRAM Usage:       <used<\/span>><\/span> of <total<\/span>><\/span>\nDisk Usage:      <used<\/span>><\/span> of <total<\/span>><\/span> (Inside the CRC VM)\nCache Usage:     <size<\/span>><\/span>\nCache Directory: \/Users\/rajesh\/.crc\/cache\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
Watch mode<\/h3>\n\n\n
crc status --watch\n<\/code><\/span><\/pre>\n\n\n
or:<\/p>\n\n\n
crc status -w\n<\/code><\/span><\/pre>\n\n\n
Use this when you want continuous status with CPU\/RAM load bars. The --watch<\/code> flag is present in v2.61.0. (GitHub<\/a>)<\/p>\n\n\n\n
JSON output<\/h3>\n\n\n
crc status -o json\n<\/code><\/span><\/pre>\n\n\n
Expected shape:<\/p>\n\n\n
{\n \"success\"<\/span>: true<\/span>,\n \"crcStatus\"<\/span>: \"Running\"<\/span>,\n \"openshiftStatus\"<\/span>: \"Running\"<\/span>,\n \"openshiftVersion\"<\/span>: \"4.21.14\"<\/span>,\n \"diskUsage\"<\/span>: 123456789<\/span>,\n \"diskSize\"<\/span>: 85899345920<\/span>,\n \"cacheUsage\"<\/span>: 1234567890<\/span>,\n \"cacheDir\"<\/span>: \"\/Users\/rajesh\/.crc\/cache\"<\/span>,\n \"ramSize\"<\/span>: 15032385536<\/span>,\n \"ramUsage\"<\/span>: 9876543210<\/span>,\n \"preset\"<\/span>: \"openshift\"<\/span>\n}\n<\/code><\/span>Code language:<\/span> JSON \/ JSON with Comments<\/span> (<\/span>json<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4.5 crc oc-env<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Adds the embedded oc<\/code> CLI to your shell PATH<\/code>.<\/p>\n\n\n\n
The docs recommend crc oc-env<\/code> when you do not already have oc<\/code> available. (crc.dev<\/a>)<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc oc-env\n<\/code><\/span><\/pre>\n\n\n
Apply it in your current shell<\/h3>\n\n\n\n
On macOS zsh\/bash:<\/p>\n\n\n
eval<\/span> \"$(crc oc-env)\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Then verify:<\/p>\n\n\n
which oc\noc version\n<\/code><\/span><\/pre>\n\n\n
Force a shell type<\/h3>\n\n\n
crc oc-env --shell zsh\ncrc oc-env --shell bash\ncrc oc-env --shell fish\ncrc oc-env --shell powershell\ncrc oc-env --shell cmd\ncrc oc-env --shell tcsh\n<\/code><\/span><\/pre>\n\n\n
The v2.61.0 source lists those shell options. (GitHub<\/a>)<\/p>\n\n\n\n
Expected output shape<\/h3>\n\n\n\n
For zsh\/bash-style shells:<\/p>\n\n\n
export PATH=\"\/Users\/rajesh\/.crc\/bin\/oc:$PATH\"<\/span>\n# Run this command to configure your shell:<\/span>\n# eval \"$(crc oc-env)\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4.6 crc console<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Open or inspect the OpenShift web console. This works for OpenShift and OKD presets, not MicroShift. The official docs say web console access is available for OpenShift and OKD presets. (crc.dev<\/a>)<\/p>\n\n\n\n
Open web console<\/h3>\n\n\n
crc console<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected output<\/h3>\n\n\n
Opening the OpenShift Web Console in<\/span> the default<\/span> browser...\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Print console URL only<\/h3>\n\n\n
crc console<\/span> --url\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected output:<\/p>\n\n\n
https:\/\/console-openshift-console.apps-crc.testing<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Print login commands and credentials<\/h3>\n\n\n
crc console<\/span> --credentials\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected output shape:<\/p>\n\n\n
To login as<\/span> a regular user, run 'oc login -u developer -p <password> https:\/\/api.crc.testing:6443'<\/span>.\nTo login as<\/span> an admin, run 'oc login -u kubeadmin -p <password> https:\/\/api.crc.testing:6443'<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Alias<\/h3>\n\n\n
crc dashboard\n<\/code><\/span><\/pre>\n\n\n
dashboard<\/code> is an alias for console<\/code> in v2.61.0. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
4.7 crc generate-kubeconfig<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Print the kubeconfig for the running CRC instance to stdout.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc generate-kubeconfig\n<\/code><\/span><\/pre>\n\n\n
Save to a file<\/h3>\n\n\n
crc generate-kubeconfig > crc-kubeconfig\nexport<\/span> KUBECONFIG=\"$PWD\/crc-kubeconfig\"<\/span>\noc whoami\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected output shape<\/h3>\n\n\n
apiVersion: v1\nclusters:\n- cluster:\n    certificate-authority-data: <base64<\/span>><\/span>\n    server: https:\/\/api.crc.testing:6443\n  name: api-crc-testing:6443\ncontexts:\n- context:\n    cluster: api-crc-testing:6443\n    user: kubeadmin\/api-crc-testing:6443\n  name: crc-admin\ncurrent-context: crc-admin\nkind: Config\nusers:\n- name: kubeadmin\/api-crc-testing:6443\n  user:\n    token: <token-or-credentials<\/span>><\/span>\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4.8 crc ip<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Print the CRC VM IP address.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc ip\n<\/code><\/span><\/pre>\n\n\n
Expected output<\/h3>\n\n\n
192.168<\/span>.130<\/span>.11<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
Common use<\/h3>\n\n\n
CRC_IP=$(crc ip)\necho \"$CRC_IP\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4.9 crc stop<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Gracefully stop the CRC instance.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc stop\n<\/code><\/span><\/pre>\n\n\n
Expected output<\/h3>\n\n\n
Stopped the instance\n<\/code><\/span><\/pre>\n\n\n
The exact success message comes from v2.61.0 source. (GitHub<\/a>)<\/p>\n\n\n\n
Force stop<\/h3>\n\n\n
crc stop --force\n<\/code><\/span><\/pre>\n\n\n
or:<\/p>\n\n\n
crc stop -f\n<\/code><\/span><\/pre>\n\n\n
Expected output if force is used:<\/p>\n\n\n
Forcibly stopped the instance\n<\/code><\/span><\/pre>\n\n\n
Use force only if normal shutdown fails or hangs. The source supports -f\/--force<\/code> on stop<\/code>. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
4.10 crc delete<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Delete the CRC VM\/instance. Use this when switching presets, upgrading CRC, fixing broken state, or reclaiming disk.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc delete<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected interactive behavior<\/h3>\n\n\n
Do you want to delete<\/span> the instance [y\/N]:\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
If confirmed:<\/p>\n\n\n
Deleted the instance\n<\/code><\/span><\/pre>\n\n\n
The source confirms that deletion is interactive unless forced, and prints \u201cDeleted the instance\u201d when the instance is deleted. (GitHub<\/a>)<\/p>\n\n\n\n
Non-interactive delete<\/h3>\n\n\n
crc delete<\/span> --force\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
or:<\/p>\n\n\n
crc delete<\/span> -f\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Delete and clear cache<\/h3>\n\n\n
crc delete<\/span> --clear-cache --force\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Use --clear-cache<\/code> when you want to remove the cached bundle and local CRC cache files too.<\/p>\n\n\n\n
\n\n\n\n
4.11 crc cleanup<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Undo host configuration changes made by crc setup<\/code>.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc cleanup\n<\/code><\/span><\/pre>\n\n\n
Expected output<\/h3>\n\n\n
Cleanup finished\n<\/code><\/span><\/pre>\n\n\n
The v2.61.0 source defines cleanup<\/code> as undoing configuration changes done by crc setup<\/code>, and its success output is exactly \u201cCleanup finished\u201d. (GitHub<\/a>)<\/p>\n\n\n\n
Clean reset flow<\/h3>\n\n\n
crc stop\ncrc delete<\/span>\ncrc cleanup\ncrc setup\ncrc start -p ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Use this when DNS, networking, virtualization, or bundle state becomes confused.<\/p>\n\n\n\n
\n\n\n\n
4.12 crc config<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
View and change CRC configuration.<\/p>\n\n\n\n
The official docs say crc config<\/code> requires a subcommand, and the available subcommands are get<\/code>, set<\/code>, unset<\/code>, and view<\/code>. (crc.dev<\/a>)<\/p>\n\n\n\n
Show config command help<\/h3>\n\n\n
crc config --help\n<\/code><\/span><\/pre>\n\n\n
Use this to see the properties your exact installed build supports.<\/p>\n\n\n\n
Important current config keys<\/h3>\n\n\n\n
Verified in v2.61.0 source:<\/p>\n\n\n
preset\nbundle\ncpus\nmemory\ndisk-size\nnameserver\npull-secret-file\ndisable-update-check\nenable-experimental-features\nenable-emergency-login\npersistent-volume-size\nenable-shared-dirs\nnetwork-mode\nhost-network-access\nhttp-proxy\nhttps-proxy\nno-proxy\nproxy-ca-file\nenable-cluster-monitoring\nmodify-hosts-file\nconsent-telemetry\nkubeadmin-password\ndeveloper-password\ningress-http-port\ningress-https-port\nenable-bundle-quay-fallback\n<\/code><\/span><\/pre>\n\n\n
Note: network-mode<\/code> is conditional in the source and may not appear in installer builds. So on your macOS installer build, trust crc config --help<\/code> as final authority. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
4.13 crc config view<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Show all configuration values you explicitly changed from defaults.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc config view\n<\/code><\/span><\/pre>\n\n\n
Expected output shape<\/h3>\n\n\n
- cpus                                  : 6<\/span>\n- memory                                : 14336<\/span>\n- pull-secret-file                      : \/Users\/<\/span>rajesh\/Downloads\/pull-secret.txt\n- preset                                : openshift\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Show secret values too<\/h3>\n\n\n
crc config view --show-secrets\n<\/code><\/span><\/pre>\n\n\n
Use carefully. It can reveal secret config values.<\/p>\n\n\n\n
Custom output format<\/h3>\n\n\n
crc config view --format '{{.ConfigKey}}={{.ConfigValue}}'<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4.14 crc config get<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Read one config value.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc config get<\/span> memory\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected output when value is set<\/h3>\n\n\n
memory : 14336\n<\/code><\/span><\/pre>\n\n\n
Expected output when value is not explicitly set<\/h3>\n\n\n
Configuration property 'memory'<\/span> is not set.\nDefault<\/span> value '<default>'<\/span> is used\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Examples<\/h3>\n\n\n
crc config get<\/span> preset\ncrc config get<\/span> cpus\ncrc config get<\/span> memory\ncrc config get<\/span> pull-secret-file\ncrc config get<\/span> consent-telemetry\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4.15 crc config set<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Set a CRC property before crc setup<\/code> or crc start<\/code>.<\/p>\n\n\n\n
Syntax<\/h3>\n\n\n
crc config set<\/span> CONFIG-KEY VALUE\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Common examples<\/h3>\n\n\n\n
Set pull secret path:<\/p>\n\n\n
crc config set<\/span> pull-secret-file ~\/Downloads\/pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Set preset to OpenShift:<\/p>\n\n\n
crc config set<\/span> preset openshift\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Set preset to OKD:<\/p>\n\n\n
crc config set<\/span> preset okd\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Set preset to MicroShift:<\/p>\n\n\n
crc config set<\/span> preset microshift\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Set CPU and memory:<\/p>\n\n\n
crc config set<\/span> cpus 6\ncrc config set<\/span> memory 14336\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Set disk size:<\/p>\n\n\n
crc config set<\/span> disk-size 80\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Set telemetry consent:<\/p>\n\n\n
crc config set<\/span> consent-telemetry yes\ncrc config set<\/span> consent-telemetry no\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Set custom developer password:<\/p>\n\n\n
crc config set<\/span> developer-password developer\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Set custom kubeadmin password:<\/p>\n\n\n
crc config set<\/span> kubeadmin-password 'MyStrongAdminPassword'\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Set proxy:<\/p>\n\n\n
crc config set<\/span> http-proxy http:\/\/proxy.example.com:<port>\ncrc config set<\/span> https-proxy http:\/\/proxy.example.com:<port>\ncrc config set<\/span> no-proxy 127.0.0.1,localhost,.testing\ncrc config set<\/span> proxy-ca-file \/path\/to\/proxy-ca.crt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Enable host access from CRC VM:<\/p>\n\n\n
crc config set<\/span> host-network-access true\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Enable cluster monitoring:<\/p>\n\n\n
crc config set<\/span> memory 14336\ncrc config set<\/span> enable-cluster-monitoring true\ncrc start\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Change ingress route ports:<\/p>\n\n\n
crc config set<\/span> ingress-http-port 8080\ncrc config set<\/span> ingress-https-port 8443\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Use this only when ports 80\/443 are unavailable on your host.<\/p>\n\n\n\n
\n\n\n\n
4.16 crc config unset<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Remove a config override and return to default.<\/p>\n\n\n\n
Syntax<\/h3>\n\n\n
crc config unset<\/span> CONFIG-KEY\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Examples<\/h3>\n\n\n
crc config unset<\/span> memory\ncrc config unset<\/span> cpus\ncrc config unset<\/span> pull-secret-file\ncrc config unset<\/span> http-proxy\ncrc config unset<\/span> https-proxy\ncrc config unset<\/span> no-proxy\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
If you omit the key, v2.61.0 returns:<\/p>\n\n\n
Please provide a configuration property to unset<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4.17 crc podman-env<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Configure your shell so a local podman-remote<\/code> client can talk to Podman inside the CRC VM.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc podman-env\n<\/code><\/span><\/pre>\n\n\n
Apply it<\/h3>\n\n\n
eval<\/span> \"$(crc podman-env)\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Rootful Podman<\/h3>\n\n\n
crc podman-env --root\n<\/code><\/span><\/pre>\n\n\n
Force shell<\/h3>\n\n\n
crc podman-env --shell zsh\ncrc podman-env --shell bash\ncrc podman-env --shell fish\ncrc podman-env --shell powershell\ncrc podman-env --shell cmd\ncrc podman-env --shell tcsh\n<\/code><\/span><\/pre>\n\n\n
Expected output shape<\/h3>\n\n\n
export CONTAINER_SSHKEY=\"\/Users\/rajesh\/.crc\/machines\/crc\/id_ecdsa\"<\/span>\nexport CONTAINER_HOST=\"ssh:\/\/core@<crc-ip>:22\/run\/user\/1000\/podman\/podman.sock\"<\/span>\nexport DOCKER_HOST=\"unix:\/\/\/Users\/rajesh\/.crc\/docker.sock\"<\/span>\n# Run this command to configure your shell:<\/span>\n# eval \"$(crc podman-env)\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Important: v2.61.0 prints a warning that podman-remote<\/code> is no longer shipped with CRC and that podman-env<\/code> will be removed in future releases. (GitHub<\/a>)<\/p>\n\n\n\n
So don\u2019t build new training material that depends heavily on this command.<\/p>\n\n\n\n
\n\n\n\n
4.18 crc bundle<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Command group for bundle operations.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc bundle\n<\/code><\/span><\/pre>\n\n\n
Expected behavior<\/h3>\n\n\n\n
Shows help for the bundle command group.<\/p>\n\n\n\n
In v2.61.0, the only verified subcommand under bundle<\/code> is:<\/p>\n\n\n
crc bundle generate\n<\/code><\/span><\/pre>\n\n\n
The v2.61.0 source adds only generate<\/code> under bundle<\/code>. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
4.19 crc bundle generate<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Generate a custom bundle from the running OpenShift cluster.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc bundle generate\n<\/code><\/span><\/pre>\n\n\n
Force-stop while generating<\/h3>\n\n\n
crc bundle generate --force-stop\n<\/code><\/span><\/pre>\n\n\n
or:<\/p>\n\n\n
crc bundle generate -f\n<\/code><\/span><\/pre>\n\n\n
The v2.61.0 source defines --force-stop\/-f<\/code> for this command. (GitHub<\/a>)<\/p>\n\n\n\n
Expected behavior<\/h3>\n\n\n\n
This is an advanced\/developer command. It operates on the running instance and creates a custom bundle. Expected output is workflow-dependent because bundle generation is handled by the machine client, not a simple static text template in the command file.<\/p>\n\n\n\n
Use this only when you intentionally need a reusable custom CRC bundle. Most normal OpenShift Local users do not<\/strong> need it.<\/p>\n\n\n\n
\n\n\n\n
4.20 crc daemon<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Internal\/hidden command that runs the CRC daemon.<\/p>\n\n\n\n
Command<\/h3>\n\n\n
crc daemon\n<\/code><\/span><\/pre>\n\n\n
Watchdog mode<\/h3>\n\n\n
crc daemon --watchdog\n<\/code><\/span><\/pre>\n\n\n
The source marks this command hidden and defines --watchdog<\/code>. (GitHub<\/a>)<\/p>\n\n\n\n
Expected behavior<\/h3>\n\n\n\n
Normal users should not run this directly. crc start<\/code> interacts with the daemon path as needed. If already running, source code can return:<\/p>\n\n\n
daemon has been started in the background\n<\/code><\/span><\/pre>\n\n\n
Use this only for debugging CRC itself.<\/p>\n\n\n\n
\n\n\n\n
4.21 crc help<\/code><\/h2>\n\n\n\n
Use case<\/h3>\n\n\n\n
Inspect your installed CLI\u2019s exact command\/flag set.<\/p>\n\n\n\n
Commands<\/h3>\n\n\n
crc help\ncrc help start\ncrc help setup\ncrc help config\ncrc help config set<\/span>\ncrc help console\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Equivalent forms<\/h3>\n\n\n
crc -h\ncrc start -h\ncrc setup -h\ncrc config -h\n<\/code><\/span><\/pre>\n\n\n
Because CRC uses Cobra, help<\/code> is available for command help. Your own crc setup -h<\/code> output is the best example of why this matters: it showed that --pull-secret<\/code> is not a setup<\/code> flag.<\/p>\n\n\n\n
\n\n\n\n
5. Preset workflows<\/h1>\n\n\n\n
CRC supports these presets:<\/p>\n\n\n
openshift   OpenShift Container Platform\nokd         OKD\nmicroshift  MicroShift\n<\/code><\/span><\/pre>\n\n\n
The docs list the minimum resources as:<\/p>\n\n\n
openshift<\/span>   4 CPUs<\/span>, 10.5<\/span> GB<\/span> RAM<\/span>, 35 GB<\/span> disk<\/span>\nokd<\/span>         4 CPUs<\/span>, 10.5<\/span> GB<\/span> RAM<\/span>, 35 GB<\/span> disk<\/span>\nmicroshift<\/span>  2 CPUs<\/span>, 4 GB<\/span> RAM<\/span>, 35 GB<\/span> disk<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
(crc.dev<\/a>)<\/p>\n\n\n\n
5.1 OpenShift preset<\/h2>\n\n\n
crc delete<\/span>\ncrc config set<\/span> preset openshift\ncrc setup\ncrc start -p ~\/Downloads\/pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected start output includes the web console, kubeadmin<\/code>, developer<\/code>, and oc login<\/code> instructions.<\/p>\n\n\n\n
5.2 OKD preset<\/h2>\n\n\n
crc delete<\/span>\ncrc config set<\/span> preset okd\ncrc setup\ncrc start\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected output is similar to OpenShift, plus an OKD note.<\/p>\n\n\n\n
5.3 MicroShift preset<\/h2>\n\n\n
crc delete<\/span>\ncrc config set<\/span> preset microshift\ncrc setup\ncrc start\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Expected output shape:<\/p>\n\n\n
Started the MicroShift cluster.\n\nUse the 'oc'<\/span> command line interface:\n  $ eval<\/span> \"$(crc oc-env)\"<\/span>\n  $ oc COMMAND\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
6. Common full examples<\/h1>\n\n\n\n
6.1 Fresh install on your Mac<\/h2>\n\n\n
crc version\ncrc config set pull-secret-file ~\/Downloads\/pull-secret.txt\ncrc setup\ncrc start\ncrc status\neval<\/span> \"$(crc oc-env)\"<\/span>\ncrc console --credentials\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Then copy the oc login<\/code> command from:<\/p>\n\n\n
crc console<\/span> --credentials\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
6.2 Start with more memory for demos<\/h2>\n\n\n
crc stop\ncrc config set<\/span> cpus 6\ncrc config set<\/span> memory 14336\ncrc start\ncrc status\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
6.3 Enable monitoring<\/h2>\n\n\n
crc stop\ncrc delete<\/span>\ncrc config set<\/span> memory 14336\ncrc config set<\/span> enable-cluster-monitoring true\ncrc setup\ncrc start -p ~\/Downloads\/pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
6.4 Configure proxy<\/h2>\n\n\n
crc stop\ncrc delete<\/span>\ncrc config set<\/span> http-proxy http:\/\/proxy.example.com:<port>\ncrc config set<\/span> https-proxy http:\/\/proxy.example.com:<port>\ncrc config set<\/span> no-proxy 127.0.0.1,localhost,.testing\ncrc config set<\/span> proxy-ca-file \/path\/to\/proxy-ca.crt\ncrc setup\ncrc start -p ~\/Downloads\/pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
6.5 Access a service running on your host from inside CRC<\/h2>\n\n\n
crc config set<\/span> host-network-access true\ncrc stop && crc start\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Then from inside the cluster\/VM side, use:<\/p>\n\n\n
host<\/span>.crc<\/span>.testing<\/span>:<port<\/span>>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
6.6 Reset everything when CRC is broken<\/h2>\n\n\n
crc stop\ncrc delete<\/span> --force\ncrc cleanup\ncrc setup\ncrc start -p ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
6.7 Upgrade CRC safely<\/h2>\n\n\n
crc stop\ncrc delete<\/span>\ncrc version\ncrc setup\ncrc start -p ~\/Downloads\/<\/span>pull-secret.txt\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
7. Commands you should run locally to verify nothing changed<\/h1>\n\n\n\n
Because you asked for \u201clatest\u201d and \u201cdo not dream,\u201d this is the safest local audit command set:<\/p>\n\n\n
crc version\ncrc help\ncrc setup -h\ncrc start -h\ncrc status -h\ncrc stop -h\ncrc delete<\/span> -h\ncrc cleanup -h\ncrc console<\/span> -h\ncrc oc-env -h\ncrc generate-kubeconfig -h\ncrc ip -h\ncrc podman-env -h\ncrc config -h\ncrc config get<\/span> -h\ncrc config set<\/span> -h\ncrc config unset -h\ncrc config view -h\ncrc bundle -h\ncrc bundle generate -h\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
For your exact Mac build, also run:<\/p>\n\n\n
crc config --help\n<\/code><\/span><\/pre>\n\n\n
That is the final authority for config keys available in your installed binary, especially conditional\/platform-specific keys like network-mode<\/code>.<\/p>\n\n\n\n
\n\n\n\n
8. Quick command cheat sheet<\/h1>\n\n\n
# Version<\/span>\ncrc version\n\n# First-time setup<\/span>\ncrc setup\n\n# Start OpenShift Local<\/span>\ncrc start -p ~\/Downloads\/pull-secret.txt\n\n# Check status<\/span>\ncrc status\n\n# Add oc to PATH<\/span>\neval<\/span> \"$(crc oc-env)\"<\/span>\n\n# Print credentials<\/span>\ncrc console --credentials\n\n# Open console<\/span>\ncrc console\n\n# Print console URL<\/span>\ncrc console --url\n\n# Export kubeconfig<\/span>\ncrc generate-kubeconfig > crc-kubeconfig\n\n# Get VM IP<\/span>\ncrc ip\n\n# Stop<\/span>\ncrc stop\n\n# Delete VM<\/span>\ncrc delete\n\n# Delete without prompt<\/span>\ncrc delete --force\n\n# Delete and clear cache<\/span>\ncrc delete --clear-cache --force\n\n# Undo setup changes<\/span>\ncrc cleanup\n\n# Show config<\/span>\ncrc config view\n\n# Get one config<\/span>\ncrc config get memory\n\n# Set config<\/span>\ncrc config set memory 14336<\/span>\n\n# Unset config<\/span>\ncrc config unset<\/span> memory\n\n# Switch preset<\/span>\ncrc delete\ncrc config set preset okd\ncrc setup\ncrc start\n\n# Advanced: generate custom bundle<\/span>\ncrc bundle generate\n\n# Internal\/debug only<\/span>\ncrc daemon\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
The big thing for your immediate issue: pull secret goes with crc start -p<\/code>, not crc setup<\/code><\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Most important daily commands Flow Commands First setup crc version \u2192 crc setup \u2192 crc start -p ~\/Downloads\/pull-secret.txt Start work crc start \u2192 crc status \u2192 crc… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[5153],"tags":[],"class_list":["post-49099","post","type-post","status-publish","format-standard","hentry","category-openshift"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49099","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=49099"}],"version-history":[{"count":3,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49099\/revisions"}],"predecessor-version":[{"id":77138,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49099\/revisions\/77138"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=49099"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=49099"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=49099"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
The install docs say newer CRC versions require manual setup, and the upgrade flow includes deleting the existing instance, replacing the binary, checking crc version<\/code>, running crc setup<\/code>, and starting the new instance. (crc.dev<\/a>)<\/p>\n\n\n\n
The docs show host.crc.testing:8080<\/code> as the pattern. (crc.dev<\/a>)<\/p>\n\n\n\n
Cluster monitoring cannot simply be disabled on an existing instance; docs say to set the property back to false and delete the existing CRC instance. (crc.dev<\/a>)<\/p>\n\n\n\n
The v2.61.0 start source has a separate MicroShift output template. (GitHub<\/a>)<\/p>\n\n\n\n
The docs show this flow for OKD. (crc.dev<\/a>)<\/p>\n\n\n\n
That message is from the source. (GitHub<\/a>)<\/p>\n\n\n\n
The docs recommend at least 14 GiB \/ 14336<\/code> MiB for cluster monitoring. (crc.dev<\/a>)<\/p>\n\n\n\n
The docs show this for accessing host services from CRC. (crc.dev<\/a>)<\/p>\n\n\n\n
The networking docs show proxy configuration using crc config set http-proxy<\/code>, https-proxy<\/code>, no-proxy<\/code>, and proxy-ca-file<\/code>. (crc.dev<\/a>)<\/p>\n\n\n\n
The docs explicitly show using consent-telemetry yes\/no<\/code>. (crc.dev<\/a>)<\/p>\n\n\n\n
The docs show changing preset before setup\/start, and list supported presets: openshift<\/code>, okd<\/code>, and microshift<\/code>. (crc.dev<\/a>)<\/p>\n\n\n\n
The source requires both a key and a value. (GitHub<\/a>)<\/p>\n\n\n\n
The source defines both output cases. (GitHub<\/a>)<\/p>\n\n\n\n
The v2.61.0 source defines --format<\/code> and --show-secrets<\/code> for config view<\/code>. (GitHub<\/a>)<\/p>\n\n\n\n
The docs list crc config view<\/code> as the way to view current non-default configuration. (crc.dev<\/a>)<\/p>\n\n\n\n
Remote\/HAProxy setup examples in the docs also use export CRC_IP=$(crc ip)<\/code>. (crc.dev<\/a>)<\/p>\n\n\n\n
The exact IP can vary by network mode\/platform. The source prints only the connection IP. (GitHub<\/a>)<\/p>\n\n\n\n
The command requires the CRC instance to exist and be running; otherwise it errors with \u201cthe CRC instance is not running, cannot retrieve kubeconfig\u201d. (GitHub<\/a>)<\/p>\n\n\n\n
The source prints exactly this form for --credentials<\/code>. (GitHub<\/a>)<\/p>\n\n\n\n
The source prints that before opening the browser. (GitHub<\/a>)<\/p>\n\n\n\n
If proxy config is enabled, crc oc-env<\/code> can also print proxy environment variables. (GitHub<\/a>)<\/p>\n\n\n\n
The v2.61.0 status command prints CRC VM status, preset status\/version, RAM usage, disk usage, cache usage, and cache directory. (GitHub<\/a>)<\/p>\n\n\n\n
That output shape is from the v2.61.0 start template. (GitHub<\/a>)<\/p>\n\n\n\n
That exact success message comes from the v2.61.0 source. (GitHub<\/a>)<\/p>\n\n\n\n
-o\/--output json<\/code> is the only supported structured output format for commands that expose the output flag. (GitHub<\/a>)<\/p>\n\n\n\n
The v2.61.0 version<\/code> command prints CRC version, OpenShift version, and MicroShift version. (GitHub<\/a>)<\/p>\n\n\n\n
The pull-secret-file<\/code> configurable property exists in v2.61.0 settings. (GitHub<\/a>)<\/p>\n\n\n\n
The v2.61.0 source defines -p<\/code> \/ --pull-secret-file<\/code> on crc start<\/code>, not on crc setup<\/code>. (GitHub<\/a>)<\/p>\n\n\n\n
The official troubleshooting flow also uses crc stop<\/code>, crc delete<\/code>, crc cleanup<\/code>, crc setup<\/code>, and crc start<\/code> for a clean state. (crc.dev<\/a>)<\/p>\n\n\n\n
Important: crc dashboard<\/code> is an alias for crc console<\/code>, and crc daemon<\/code> is marked hidden\/internal in the source. (GitHub<\/a>)<\/p>\n\n\n\n
(GitHub<\/a>)<\/p>\n\n\n\n