-
Notifications
You must be signed in to change notification settings - Fork 37
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
Prevent mount point collision on validation #258
Labels
good first issue
Good for newcomers
help wanted
Requires help from contributors to get done
kind/feature
New feature or request
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Comments
This issue is stale because it has been open 60 days with no activity. |
This is still needed. |
For now we are saying that any issues are user error and we dont care rn |
This issue is stale because it has been open 60 days with no activity. |
Didn't we add check for that somewhere? Maybe @jmickey you know more. |
This issue was closed because it has been stalled for 365 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for newcomers
help wanted
Requires help from contributors to get done
kind/feature
New feature or request
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Describe the solution you'd like:
It is possible to set multiple volumes to be mounted to the same path. We can assume the end-user knows what they are doing, but should be a very straightforward validation.
Why do you want this feature:
To prevent unnecessary failures because of user error.
Anything else you would like to add:
Validate 2 things:
/
Reference: #241 (comment)
The text was updated successfully, but these errors were encountered: