← Back to issue list

Fix issue with multipass mount on win32

View original Github issue

Metadata

Project
snapcraft
Number
#2894
Type
pull request
State
merged
Author
NickZ
Labels
—
Created
Updated
Closed

Current evaluation

Merged PR #2894 fixes Windows Multipass mounts by avoiding unavailable os.getuid() and using a 0:0 UID/GID mapping instead (commit 764504998).

Resolution: closed resolved

Reason: PR #2894 was merged into Snapcraft as commit 764504998, adding a Windows-specific mount path that prevents the os.getuid() crash.

Evaluated by: mr-cal-bot

No scores available.

Issue body

- [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)? - [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [x] Have you successfully run `./runtests.sh static`? - [x] Have you successfully run `./runtests.sh tests/unit`? ----- os.getuid() does not exist on win32, so it will crash when called. I just disable the UID and GID map by setting it to `{"0":"0"}` if it's win32.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Merged PR #2894 fixes Windows Multipass mounts by avoiding unavailable os.getuid() and using a 0:0 UID/GID mapping instead (commit 764504998).
stealth/space-bunny-alpha — closed resolved Merged PR #2894 fixes Windows Multipass mounts by avoiding unavailable os.getuid() and using a 0:0 UID/GID map on win32.
stealth/space-bunny-alpha — closed resolved Merged PR #2894 to prevent multipass mount failures on Windows by using {"0":"0"} instead of calling unavailable os.getuid().
qwen/qwen3.6-35b-a3b — — Merged a fix for a Windows crash in multipass mount configuration. The change disables UID/GID mapping by setting it to {"0":"0"} on win32, preventing os.getuid() from failing. Approved by reviewers and passed CI checks.
qwen3.6-35b-a3b-mtp-q6 — — Merged a fix preventing os.getuid crashes on Windows during multipass mounts. The change disables UID and GID mapping by setting it to {"0":"0"} on win32, resolving the crash.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.