`limactl start` should start `$LIMA_INSTANCE` rather than `default`?
Open
area/cli
impact/breaking
impact/changelog
- Dominant language
- Go
- Stars
- 21.9k
- Forks
- 957
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 53
Description
https://github.com/lima-vm/lima/blob/69751d55f37977edbecc6222b746e1b7b73b08cf/cmd/lima#L14
While the `lima` wrapper allows overriding `default` via an environment variable `$LIMA_INSTANCE`, the `limactl` CLI doesn't recognize this variable.
We may change the behavior of `limactl` to respect the env var, however, this kind of breaking change should probably happen when bumping up the major version (i.e., Lima v3.0)
Contributor guide
Assessment
This issue has not been assessed yet.