We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Lima does not support mounting locations containing whitespace, e.g.
mounts: - location: "~/foo bar" writable: true
This obviously affects users whose host username contains a space.
Known problem spots:
lima.env
LIMA_CIDATA_MOUNTS_NNN_MOUNTPOINT
reversesshfs.Prepare
mkdir -p
reversesshfs.Start
sshfs
There are probably more...
The text was updated successfully, but these errors were encountered:
Don't just source lima.env; value might include spaces
34b03da
Instead copy the code from Lima's boot.sh. This is required to fix lima-vm/lima#933 Signed-off-by: Jan Dubois <[email protected]>
Quote local and remote filenames in case they include spaces
7ed7e03
This is required because the names are sent as a single string over ssh. This (together with lima-vm/alpine-lima#98) will fix lima-vm/lima#933. Signed-off-by: Jan Dubois <[email protected]>
Successfully merging a pull request may close this issue.
Description
Lima does not support mounting locations containing whitespace, e.g.
This obviously affects users whose host username contains a space.
Known problem spots:
lima.env
does not quoteLIMA_CIDATA_MOUNTS_NNN_MOUNTPOINT
reversesshfs.Prepare
doesn't quote the argument tomkdir -p
reversesshfs.Start
doesn't quote the local and remote path arguments tosshfs
There are probably more...
The text was updated successfully, but these errors were encountered: