Charro Gruver
Charro Gruver
Yeah, it's not always immediate. I was able to login to the local registry, and run several oc commands. Then, after sitting idle for just a couple of minutes, it...
It looks OK. `1d2ecc66a3d9a947cc49fae169060b36079f00c34233d4645011bff360fa4902`
Weird... It may be an M2 thing... Or, maybe I have something installed that is causing issues... I might try a full reset of the MacBook and just install crc...
I built the `crc` executable from the `v2.9.0` tag and am testing with the `4.11.3` bundle. So far, so good... If things continue to look good, I'll close this tomorrow...
The `4.11.3` bundle with `v2.9.0` of crc seems to be stable. I was able to deploy workloads, manipulate images with Podman, and restart the OpenShift instance several times. I'll try...
> > I built the crc executable from the v2.9.0 tag and am testing with the 4.11.3 bundle. > > For completeness, would be great if you can test this...
I saw disk corruption periodically with `v2.8.0` as well. When it happens, you have to delete the VM. Otherwise, when it boots, it drops straight into the emergency shell.
I'm going to keep running tests on the `v2.9.0 + 4.11.3` instance. If it remains stable, I'll close this after `v2.9.0` officially drops.
One more run with `v2.9.0` and the older `4.11.1` bundle. Same test as before, deploy Quarkus app, different failure that looks like what I posted above. Sometimes kernel panic, sometimes...
FWIW, `v2.9.0 + 4.11.3` still looks good.