-
-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
colima start does not honor default config, but then overwrites it #985
Comments
I have exactly the same problem on the same setup |
@abiosoft I am facing the same issue very first it's working fine colima start --vm-type vz --network-address --cpu 6 --memory 8 --arch aarch64
|
I have same problem. Fix please. |
I'm also having trouble with the same problem on my M3 Mac. Even if I rewrite the VM type of I would appreciate it if it would be fixed as soon as possible. |
Hi guys, same problem occurred here on my Mac M3 (Sonoma) after
Best regards, P.S.: Attention ... by doing so I hade to re-load all images/containers! |
I have the same issue and a very naive solution worked for me. Definitely not a fix but restarting my computer worked. Have you tried turning it off and on again? |
This issue also affects M1 Pro. Previously, colima 0.6.8 was functioning properly before updating macOS to the recent version. Actually, I was not manually triggering
After that I rebooted
Might be related to: lima-vm/lima#2227 |
The only way I got it working, thanks! |
I encountered the same issue. After running this command, it worked fine.
|
Description
The
vz
VM type does not work on my M3 Mac, so I must useqemu
. My config at~/.config/default/colima.yaml
hasvmType: qemu
so that when I runcolima start
I should use theqemu
VM type. Instead it goes with thevz
type, and overwrites the config file as well. It also fails for this same reason when runningbrew services start colima
, and indeed overwrites the config too. I am able to runcolima start --edit
, see that it has already overwritten thevmType
, edit it toqemu
, then exit and it will work, but a simplecolima start
fails. The only way I have ever gotten it to work in brew services temporarily is to runcolima delete
then reinstall colima, but it breaks again after some time, and I am not sure what triggers it, possibly a reboot.Version
colima version 0.6.8
git commit: 9b0809d
limactl version 0.20.1
qemu-img version 8.2.1
Operating System
Output of
colima status
If I run
colima start
, thencolima status
:If I run
colima start --edit
, and edit it toqemu
, then runcolima status
:Reproduction Steps
vmType: qemu
in~/.colima/default/colima.yaml
.colima start
.vmType: vz
Expected behaviour
colima start
should run the profile in the config and not overwrite the config.Additional context
colima start
gives the following:The text was updated successfully, but these errors were encountered: