lima
lima copied to clipboard
Linux virtual machines, with a focus on running containers
Improves the error message, when using a top-level directory by mistake. ```console $ mkdir -p /tmp/foo/bar $ LIMA_HOME=/tmp/foo _output/bin/limactl ls WARN[0000] The directory "/tmp/foo" does not look like a valid...
Make it possible to fill in the defaults (null) with limactl validate, with a workaround for python yaml. Was using a local patched version to test with the jsonschema and...
Add a simple unit test for some coverage
Make sure that it is possible to parse default.yaml to the expected LimaYAML structure Add some minor changes, to make the internal representation (before defaults) "pretty" Left to do is...
Avoid issues with converting null strings in a map value Change order to alphabetical, to match the "limactl info" ---- Helps with: * https://github.com/lima-vm/lima/pull/1069 * https://github.com/lima-vm/lima/pull/2306
This PR moves the compiled regexp outside the functions to prevent it from being recompiled each time these functions are called. Some regexp moved out of loops to save readability.
Closes #2282 ~~Needs docs.~~ ---- lima.yaml (based on debian.yaml) ```yaml ... provision: - mode: ansible playbook: playbook.yaml ``` inventory.yaml (auto-generated) ```yaml lima: hosts: ansible: ansible_connection: ssh ansible_host: lima-ansible ansible_ssh_common_args: -F...
Display an error message, when trying to put $LIMA_HOME on NFS network filesystem (instead of local filesystem) Closes #2325
Well, at least not initially. [Update: it seems to start, but hostagent cannot connect to it] We've observed this multiple times with Rancher Desktop after switching to Lima 0.19.0 (https://github.com/rancher-sandbox/rancher-desktop/issues/6151)....