crc: CRC cannot be started anymore mac
General information
Unable to start CRC on a MAC macOS version 15.1.1
When starting I get the following errors
INFO Using bundle path /Users/rmestrum/.crc/cache/crc_vfkit_4.17.7_arm64.crcbundle
INFO Checking if running macOS version >= 13.x
INFO Checking if running as non-root
INFO Checking if crc-admin-helper executable is cached
INFO Checking if running on a supported CPU architecture
INFO Checking if crc executable symlink exists
INFO Checking minimum RAM requirements
INFO Check if Podman binary exists in: /Users/rmestrum/.crc/bin/oc
INFO Checking if running emulated on Apple silicon
INFO Checking if vfkit is installed
INFO Checking if old launchd config for tray and/or daemon exists
INFO Checking if crc daemon plist file is present and loaded
INFO Checking SSH port availability
INFO Loading bundle: crc_vfkit_4.17.7_arm64...
INFO Creating CRC VM for OpenShift 4.17.7...
INFO Generating new SSH key pair...
INFO Generating new password for the kubeadmin user
INFO Starting CRC VM for openshift 4.17.7...
INFO CRC instance is running with IP 127.0.0.1
INFO CRC VM is running
INFO Updating authorized keys...
INFO Resizing /dev/vda4 filesystem
INFO Configuring shared directories
INFO Check internal and public DNS query...
WARN Failed public DNS query from the cluster: ssh command error:
command : curl --head quay.io
err : Process exited with status 6
:
INFO Check DNS query from host...
INFO Verifying validity of the kubelet certificates...
INFO Starting kubelet service
INFO Waiting for kube-apiserver availability... [takes around 2min]
INFO Adding user's pull secret to the cluster...
INFO Updating SSH key to machine config resource...
INFO Waiting until the user's pull secret is written to the instance disk...
Failed to update pull secret on the disk: Temporary error: pull secret not updated to disk (x2)
failed to read /var/lib/kubelet/config.json file: ssh command error:
command : sudo cat /var/lib/kubelet/config.json
err : Process exited with status 1
: /bin/bash: Input/output error
Operating System
macOS
Hypervisor
vfkit
Did you run crc setup before crc start?
yes
Running on
Laptop
Steps to reproduce
- Download the latest version of CRC (2.45.0+7aeb3b in my case)
- Run crc setup
- Run crc start -p <location to pullsecret>
CRC version
❯ crc version
CRC version: 2.45.0+7aeb3b
OpenShift version: 4.17.7
MicroShift version: 4.17.7
CRC status
❯ crc status
CRC VM: Running
OpenShift: Unreachable (v4.17.7)
RAM Usage: 0B of 0B
Disk Usage: -1B of -1B (Inside the CRC VM)
Cache Usage: 38.87GB
Cache Directory: /Users/rmestrum/.crc/cache
CRC config
❯ crc config view
- consent-telemetry : no
- disk-size : 100
- memory : 14000
Host Operating System
❯ sw_vers
ProductName: macOS
ProductVersion: 15.1.1
BuildVersion: 24B91
Expected behavior
CRC starts and runs so it can be used.
Actual behavior
CRC starts gives error and CRC is not usable
CRC Logs
https://gist.github.com/rmestrum/9cb779c0c94770e7c81940d3794f760f
Additional context
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 28 (11 by maintainers)
Commits related to this issue
- vfkit: Update to latest version (0.6.1) This may fix these issues: #3410, #4513 — committed to likeablob/crc by likeablob 2 years ago
- vfkit: Update to latest version (0.6.1) This may fix these issues: #3410, #4513 — committed to crc-org/crc by likeablob 2 years ago
- vfkit: Update to latest version (0.6.1) This may fix these issues: #3410, #4513 — committed to lilyLuLiu/crc by likeablob 2 years ago
Hi, I encountered the same issue (on an M4 Pro Macbook Pro, crc 2.49.0+e843be). In my case, the VM is unstable and crashes, showing the following disk errors in kmsg:
I’m not 100% sure, but updating the bundled
vfkitfrom v0.5.0 to v0.6.1 seems to have fixed the issue.Possibly related:
CRC version
EDIT: added https://github.com/crc-org/crc/issues/3410
This morning I received a notification concerning an update to macOS version 15.3.2. So I applied this update. My laptop was restarted. Then here is what i did (I already have the pull-secrect.txt in my home directory).
cd crc stop -f crc delete -f crc cleanup crc setup crc config set pull-secret-file $(pwd)/pull-secret.txt crc start
INFO Using bundle path /Users/philou/.crc/cache/crc_vfkit_4.18.1_arm64.crcbundle INFO Checking if running macOS version >= 13.x
INFO Checking if running as non-root
INFO Checking if crc-admin-helper executable is cached INFO Checking if running on a supported CPU architecture INFO Checking if crc executable symlink exists
INFO Checking minimum RAM requirements
INFO Check if Podman binary exists in: /Users/philou/.crc/bin/oc INFO Checking if running emulated on Apple silicon INFO Checking if vfkit is installed
INFO Checking if old launchd config for tray and/or daemon exists INFO Checking if crc daemon plist file is present and loaded INFO Checking SSH port availability
INFO Loading bundle: crc_vfkit_4.18.1_arm64…
INFO Creating CRC VM for OpenShift 4.18.1…
INFO Generating new SSH key pair…
INFO Generating new password for the kubeadmin user INFO Starting CRC VM for openshift 4.18.1…
INFO CRC instance is running with IP 127.0.0.1
INFO CRC VM is running
INFO Updating authorized keys…
INFO Configuring shared directories
INFO Check internal and public DNS query…
INFO Check DNS query from host…
INFO Verifying validity of the kubelet certificates… INFO Starting kubelet service
INFO Waiting for kube-apiserver availability… [takes around 2min] INFO Adding user’s pull secret to the cluster…
INFO Updating SSH key to machine config resource… INFO Waiting until the user’s pull secret is written to the instance disk… INFO Changing the password for the kubeadmin user INFO Updating cluster ID…
INFO Updating root CA cert to admin-kubeconfig-client-ca configmap… INFO Starting openshift instance… [waiting for the cluster to stabilize] INFO Operator authentication is progressing
INFO Operator console is progressing
INFO All operators are available. Ensuring stability… INFO Operators are stable (2/3)…
INFO Operators are stable (3/3)…
INFO Adding crc-admin and crc-developer contexts to kubeconfig… Started the OpenShift cluster.
The server is accessible via web console at: https://console-openshift-console.apps-crc.testing
IT WORKS NOW. I can log in to the cluster. I don’t know exactly what change I did (I go thru my history in terminal). Or is it the new macOS version … don’t know. I still have vmware fusion 13.x (not running) and Docker (not running) on my laptop.
https://www.redhat.com/en/topics/edge-computing/microshift explain what is microshift and if you want to consume it then kubeconfig file already added for same so you can run
oc get pods -Aand other queries using oc command.