abiosoft
commented
1 year ago It looks like it is stuck in an unknown state. You can resolve that by forcefully shutting it down.
colima stop -fOpen Amit-Thawait opened 1 year ago
abiosoft
commented
1 year ago It looks like it is stuck in an unknown state. You can resolve that by forcefully shutting it down.
colima stop -f
Amit-Thawait
commented
1 year ago It didn't worked. The difference I can see in logs is that
For successful startup we get
* Registering QEMU binaries in binfmt misc ... [ ok ]
* Starting sshd ... [ ok ]For my failure case, we get the below logs
* Registering QEMU binaries in binfmt misc ... [ ok ]
No user exists for uid 0
* ERROR: sshd failed to start@abiosoft Do you have any idea why would the error No user exists for uid 0 would come
abiosoft
commented
1 year ago Can you try with another profile?
# create another profile named 'sample'
colima start sampleIf it still fails, can you try starting with --cpu-type host or --cpu-type max?
flowy0
commented
1 year ago 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.
Amit-Thawait
commented
1 year ago 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 https://github.com/abiosoft/colima/issues/684#issuecomment-1545228327, 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
framp
commented
1 year ago I have a similar issue after upgrading to Ventura, Intel Macbook 2019, colima 0.5.4
rm -rf ~/.lima ~/.colimadoesn't fix it
trying different parameters or colima start doesn't fix it
❯ colima start -v
INFO[0000] starting colima
INFO[0000] runtime: docker
INFO[0000] preparing network ... context=vm
INFO[0000] creating and starting ... context=vm
> Terminal is not available, proceeding without opening an editor
> "Attempting to download the image from \"https://github.com/abiosoft/alpine-lima/releases/download/colima-v0.5.0-2/alpine-lima-clm-3.16.2-x86_64.iso\"" digest="sha512:e9e118498f3a0745574ffc3686105d2c9777f7142164fe50ee47909dabd504c80ac29aeb76f9582706173310d1488d3b6f0ee9018e2a6aadc28eefb7767b63ec"
> Using cache "/Users/framp/Library/Caches/lima/download/by-url-sha256/e1cbaef56fc8e75af106d934389a17618643fcecfa066302d45ffb0390709851/data"
> [hostagent] Starting QEMU (hint: to watch the boot progress, see "/Users/framp/.lima/colima/serial.log")
> SSH Local Port: 55136
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
> [hostagent] Driver stopped due to error: "exit status 255"
> [hostagent] Shutting down the host agent
> [hostagent] failed to exit SSH master
> [hostagent] Shutting down QEMU with ACPI
> [hostagent] failed to open the QMP socket "/Users/framp/.lima/colima/qmp.sock", forcibly killing QEMU
> [hostagent] failed to kill QEMU
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"Can anyone try new v0.5.5?
rfay
commented
1 year ago (v0.5.5 isn't quite in homebrew yet, but I assume someone will push it soon)
lucabergamini
commented
1 year ago Same issue on 0.5.4. Multiple stops didn't help.
I've updated to 0.5.5 with brew and run:
limactl stop -f colima
colima start --cpu 4 --memory 4 --disk 100 --arch aarch64 --vm-type=vz --vz-rosettaand 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
terev
commented
1 year ago 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.
abiosoft
commented
1 year ago @terev what's your macOS version? Are you on an m1 device?
terev
commented
1 year ago @abiosoft on an m1 yeah.
ProductName: macOS
ProductVersion: 13.2.1Posted on a lima issue here too https://github.com/lima-vm/lima/issues/1200#issuecomment-1568669912
abiosoft
commented
1 year ago @terev you're most likely affected by this https://github.com/lima-vm/lima/issues/1399 which requires an upgrade to macOS 13.3.1 or newer.
terev
commented
1 year ago @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?
AnhQKatalon
commented
1 year ago I met the same issue and it was gone after I updated to MacOS 13.5. Thank you so much @abiosoft
ejames17
commented
1 year ago Same issue but upgrading to 13.5 did not help unfortunately. :(
damienmckenna
commented
1 year ago 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.
ejames17
commented
1 year ago @damienmckenna I was able to resolve this doing a factory reset on the instance.
damienmckenna
commented
1 year ago FWIW I ended up switching to OrbStack.
andrewmed-prop
commented
1 year ago Hello I am observing the same behavior Running Sonoma 14.1
Deleting VM helps, but I can not start existent instance
damienmckenna
commented
1 year ago FWIW I replaced Colima with Orbstack and haven't had any problems since.
ViViDboarder
commented
1 year ago 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 limactl as well. Logs are boring and the same as those shown here.
Unlike some others, I have no luck when deleting everything and starting fresh. I just uninstalled colima and lima, cleared out ~/.colima ~/.lima, re-installed them (colima v0.6.1 and lima 0.18.0), and tried to run the default VM and got the same thing.
nicolasbrechet
commented
1 year ago 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 The only way to continue using Colima has been to revert to v0.5.6...
LedzZm
commented
1 year ago @nicolasbrechet How did you revert?
terev
commented
1 year ago Same here. I think I'm experiencing this issue much more often in this release https://github.com/lima-vm/lima/issues/1609 .
@LedzZm go install github.com/abiosoft/colima/cmd/colima@v0.5.6 was the easiest way I found to install an old version. ~/go/bin would need to be in your path or run it directly, or move it to be in your path, etc.
LedzZm
commented
1 year ago Anyone using brew for downgrading?
LedzZm
commented
12 months ago For me this is still an issue in v 0.6.5 I upgraded qemu as well to 8.1.3
terev
commented
11 months ago @LedzZm A change was pushed to lima that helps this boot issue. Try brew install lima --HEAD .
rfay
commented
11 months ago Related QEMU failure and update info in
nicolasbrechet
commented
7 months ago @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). Anyway since it was almost 6 months ago, I hope you don't have this issue anymore.
mokkun
commented
3 months ago 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