Skip to content
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

[mounts] Allow only one-to-one uid/gid mappings for mounts #3332

Open
andrei-toterman opened this issue Dec 14, 2023 · 0 comments · May be fixed by #3349
Open

[mounts] Allow only one-to-one uid/gid mappings for mounts #3332

andrei-toterman opened this issue Dec 14, 2023 · 0 comments · May be fixed by #3349
Assignees
Labels
Milestone

Comments

@andrei-toterman
Copy link
Contributor

Describe the bug
When specifying uid/gid mappings for a mount, you can use the same uid/gid in more than one mapping. This creates confusion as it is not clear which map should be used.

To Reproduce
How, and what happened?

  1. multipass mount dir instance:dir -u 1000:2000 -u 1000:3000 -u 3000:2000
  2. Now it's not clear if a host file owned by 1000 should be owned 2000 or 3000 in the VM or if a remote file owned by 2000 should be owned by 1000 or 3000 on the host.

Expected behavior
Throw an error when an attempted mount does not have a one-to-one correspondence between its mapped uids/gids.

@andrei-toterman andrei-toterman added bug needs triage Issue needs to be triaged labels Dec 14, 2023
@ricab ricab removed the needs triage Issue needs to be triaged label Dec 15, 2023
@sharder996 sharder996 linked a pull request Jan 2, 2024 that will close this issue
@sharder996 sharder996 self-assigned this Jan 2, 2024
@sharder996 sharder996 added this to the 1.14.0 milestone Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants