fix: respect LIMA_HOME environment variable #3254
Merged
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.
What does this PR do?
In some environments, it might be desirable to not use the regular
HOME
environment variable (~
)...For instance, when /home is on a shared filesystem but you want your instances on a local filesystem.
In those cases, you can override
LIMA_HOME
Note: the LIMA_HOME defaults to
~/.lima
See https://github.com/lima-vm/lima/blob/master/docs/internal.md#lima-home-directory-lima_home
Screenshot/screencast of this PR
What issues does this PR fix or reference?
How to test this PR?
export LIMA_HOME=/tmp/home/lima
See that it is looking for sockets there:
[lima] Could not find podman socket at /tmp/home/lima/podman/sock/podman.sock
Could also verify that it still works OK.