Colima start stuck at Waiting for the essential requirement 1 of 5: "ssh" #684
Comments
|
It looks like it is stuck in an unknown state. You can resolve that by forcefully shutting it down. |
|
It didn't worked. For successful startup we get For my failure case, we get the below logs @abiosoft Do you have any idea why would the error |
|
Can you try with another profile? # create another profile named 'sample'
colima start sampleIf it still fails, can you try starting with |
|
I encountered this error. |
|
But deleting the instance will also wipe out the previous data.
I know that starting from clean slate solves the issue but I lost my local
database data.
Hence I was seeking suggestions on how can I recover from that state
On Fri, 12 May 2023 at 8:17 AM, Gayle ***@***.***> wrote:
I encountered this error.
I deleted the default instance and restarted colima start -a x86_64 --cpu
4 --memory 8 --disk 80, it seemed to fix the issue.
—
Reply to this email directly, view it on GitHub
<#684 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJJ5H7M4RX3NP56EXDQZWDXFXIWDANCNFSM6AAAAAAWRPCGJ4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Regards,
Amit Thawait
Phone : +91-8080686735
|
|
I have a similar issue after upgrading to Ventura, Intel Macbook 2019, colima 0.5.4 doesn't fix it trying different parameters or |
|
Can anyone try new v0.5.5? |
|
(v0.5.5 isn't quite in homebrew yet, but I assume someone will push it soon) |
|
Same issue on I've updated to and that worked. However, I got an EOF after some time the containers were running and after that point nothing worked except deleting the vm. I should add I got into the ssh issue after an EOF in the first place though |
|
Experiencing this same issue after upgrading to Colima 0.5.5 . Starting a new vz vm seems to hang waiting for the ssh port. ~/.lima/colima/serial.log seems to be empty for me. |
|
@terev what's your macOS version? Are you on an m1 device? |
|
@abiosoft on an m1 yeah. Posted on a lima issue here too lima-vm/lima#1200 (comment) |
|
@terev you're most likely affected by this lima-vm/lima#1399 which requires an upgrade to macOS 13.3.1 or newer. |
|
@abiosoft Thank you! that was it. Its working now on 13.4. Maybe it could be worth adding something about this to the release notes? |
|
I met the same issue and it was gone after I updated to MacOS 13.5. Thank you so much @abiosoft |
|
Same issue but upgrading to 13.5 did not help unfortunately. :( |
|
Am seeing this after my computer was replaced with one running Ventura; under Monterey it was fine, but with Ventura it has been incredibly unreliable. The OS and all pieces of Colima (via Homebrew) are up to date, starting a project using ddev (a wrapper for Docker containers) results in Colima failing after a while. I've spent so much time debugging it I could have easily paid for a year's subscription to Docker. |
|
@damienmckenna I was able to resolve this doing a factory reset on the instance. |
|
FWIW I ended up switching to OrbStack. |
|
Hello I am observing the same behavior Deleting VM helps, but I can not start existent instance |
|
FWIW I replaced Colima with Orbstack and haven't had any problems since. |
|
I've been having the issue for a while now on macOS 13.6. Colima (and Lima) won't start and no serial logs are captured. For what it's worth, it seems to be happening with Unlike some others, I have no luck when deleting everything and starting fresh. I just uninstalled |
|
Running on macOS 13.6 (22G120) on a MBP (15-inch, 2019). I had the same issue with Colima 0.6.2, removing Colima & lima didn't solve my issue. Starting with a fresh instance didn't work |
|
@nicolasbrechet How did you revert? |
|
Same here. I think I'm experiencing this issue much more often in this release lima-vm/lima#1609 . @LedzZm |
|
Anyone using brew for downgrading? |
|
For me this is still an issue in v 0.6.5 |
|
@LedzZm A change was pushed to lima that helps this boot issue. Try |
|
Related QEMU failure and update info in |
|
@LedzZm sorry I didn't see your comment until now. If I remember correctly, I had Colima installed with Brew, so I uninstalled it from Brew, then manually installed the older version (downloaded from the releases). |
|
Having this issue with Colima v0.6.10 on macOS Sonoma 14.5. First time trying to use it, and pretty much stuck with this issue. |
Description
I am using Mac Intel (12.6.1)
colima start command is stuck at
Version
Colima Version: 0.5.4
Lima Version:
Qemu Version:
Operating System
Output of
colima statusFATA[0000] error retrieving current runtime: empty value
Reproduction Steps
colima start --cpu 4 --memory 12 --disk 100colima startwithout any argsExpected behaviour
No response
Additional context
serial.log
The text was updated successfully, but these errors were encountered: