Open lgrossma opened 2 months ago
Same thing was happening to me before the first crc start
right after installing the crc
After the complete re-installation of CRC I cannot reproduce the issue (the previous attempt wasn't successful, imho, due to lack of available disk space, which wasn't reported by the wizard).
Stop Cluster
/Start Cluster
work well for me with the same CRC version used:
crc" version -o json
{
"version": "2.41.0",
"commit": "e6495f",
"openshiftVersion": "4.16.7",
"microshiftVersion": "4.16.7"
}
Your errors look like no CRC executable was found on the system (f.i. if you invoked npm i; npm run build
and the last one didn't finished successfully while the running extension was continuing its execution) - spawn null ENOENT
- there should be a crc ...
-like tool command specified instead of nul
.
@lgrossma Also, if you're still able to reproduce the issue, could you please check the extension openshiftToolkit.crcBinaryLocation
preference value - when the issue is reproducible I expect it to be empty or null...
After stopping a crc cluster and then trying to start it again, I am running into errors
https://github.com/user-attachments/assets/87f63f90-407a-4aaa-a776-d5762e8bbaa0