Skip to content
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 appears to overwrite lima.yaml with defaults at each launch #106

Closed
spkane opened this issue Jan 11, 2022 · 4 comments
Closed

Comments

@spkane
Copy link

spkane commented Jan 11, 2022

I am trying to get shared networking setup (https://github.com/lima-vm/lima/blob/master/docs/network.md#managed-vmnet-networks-via-vde_vmnet), but each time I add a few lines to ~/.lima/colima/lima.yaml and then run colima start --cpu 8 --memory 8 --disk 100 --runtime containerd --with-kubernetes those lines vanish and the files looks exactly like it did before my edits.

Am I doing something wrong? Or is colima clobbering this?

@jandubois
Copy link

Or is colima clobbering this?

It probably is. Put your settings into an override.yaml file as I explained in #105 (comment).

These settings will be merged with the lima.yaml content when the VM is started.

The merged state is not visible to limactl ls, even though they were applied; I've created lima-vm/lima#510 to (eventually) deal with this.

@spkane
Copy link
Author

spkane commented Jan 12, 2022

Great. Thank you. I will give that a try.

@spkane
Copy link
Author

spkane commented Jan 12, 2022

That appears to have worked. Thanks!

@abiosoft
Copy link
Owner

@spkane that is the recommended way as colima dynamically generates the lima config on each start.

Thanks again @jandubois.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants