-
-
Notifications
You must be signed in to change notification settings - Fork 420
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
Defaults for start arguments? #242
Comments
I've been confused about what arguments are only useful for first launch, and which must be done later. For example, if you start the first time with And what about Thanks! |
I agree that the documentation can be better in this regard. However, proper config file support is in the works.
DNS does not persist, it needs to be specified on each startup. |
How about |
Yeah they all persist, |
This is actually specified in
|
Thanks! That always scrolled off the screen for me :) So only |
Yeah, you can always customize an existing VM with the exception of disk size as stated here https://github.com/abiosoft/colima#customization-examples.
|
Hmm, you said in #242 (comment) "They all persist, DNS is the exception" So the doc says but you're saying that if you use |
Yes :) I can now see how this gets easily confusing. |
Is there a way (like dotfile) for colima to specify the
--memory
--cpu
flags instead of doing that each time?Instead of typing:
colima start --cpu 4 --memory 8
I could do something like
colima start
And it would read from
~/.colima/config.yml
or something with:Not sure if this is a question or a feature request ;)
The text was updated successfully, but these errors were encountered: