Lima: allow setting (minimum) disk size #9276
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Mark Yen <[email protected]>
This adds a field to specify the desired disk size; it accepts a string like `100GiB`, and does not support shrinking the disk. Signed-off-by: Mark Yen <[email protected]>
This adds a check to see if the user has a lima override file set, and disk sizes set within that. If this is present, it breaks our settings for the disk size. Signed-off-by: Mark Yen <[email protected]>
Signed-off-by: Mark Yen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new non-UI preference,
experimental.virtual-machine.disk-size, that takes the same sort of value as found in the Lima configuration; Lima will automatically expand the disk to be that size.A diagnostic is also attached, so that if the user has the manual override set, they can be warned that they should remove it (so that they can use our built-in configuration instead).
Fixes #1521