-
-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
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
Incorrect detection of overlapping mounts when 1 name is a substring #108
Comments
I tried the .aws_legacy directory with the name .aws-legacy first, and renamed it in case it was a word-separator issue. It still doesn't work when the directory is called .awslegacy. |
See lima-vm/lima#302 |
But these don't overlap! |
This was my attempt to workaround lima-vm/lima#302 |
Oops, sorry, looks like the check for overlapping mounts is in colima, and is just doing substring matches. So you should try renaming |
That works. So it is the check that is at fault. |
Yes, it is a simple colima/environment/vm/lima/yaml.go Line 200 in d99e306
@abiosoft I would "normalize" the names before comparison by making sure each mount ends with a |
colima version 0.2.2
git commit: b2c7697
I would expect this to work, instead of the error message that is displayed.
I guess it might be a problem with lima, not colima itself.
The text was updated successfully, but these errors were encountered: