root user handling for multipass is confusing
Metadata
Current evaluation
Fixed by merged snapcore/snapcraft#2385 (commit 404255671), consolidating CLI re-execution and delegating Multipass root handling to build-provider APIs.
Resolution: closed resolved
Reason: The issue's closing comment links PR #2385, and repository history confirms it merged as commit 404255671, titled "cli: consolidate re-execution."
Evaluated by: mr-cal-bot
No scores available.
Issue body
When shelling in, you are not really root, so handling of files becomes complicated as snapcraft re-executes itself as root making things complex.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged snapcore/snapcraft#2385 (commit 404255671), consolidating CLI re-execution and delegating Multipass root handling to build-provider APIs. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #2385 (commit 404255671), consolidating CLI re-execution and delegating Multipass root-user handling to build-provider APIs. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as stale after inactivity, with no comments, linked fix, or documented resolution for the confusing root handling in Multipass. | |
| qwen/qwen3.6-35b-a3b | — | — | Multipass root user handling confusion was closed without resolution or comments. The report appears abandoned or marked stale due to inactivity, with no fix implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The reported complexity around root user handling in multipass and snapcraft re-execution was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Multipass root user handling confusion was closed without resolution. Zero comments indicate the report was abandoned without a fix. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The multipass root handling issue was abandoned due to inactivity and zero comments. No fix or workaround was implemented. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#2385
(confidence 100%)
Merged as commit 404255671 and cited directly in the issue's closing comment.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1792614 use multipass if set in the environment | snapcraft (launchpad) | closed | Closed as fixed: PR snapcore/snapcraft#2275 (commit 04f8896d9) made SNAPCRAFT_BUILD_ENVIRONMENT/multipass take precedence over the base-derived provider choice. | |
| #2447 build providers: remove SIGUSR1 signal ignore workaround for multipass | snapcraft | merged | Merged PR #2447 (commit a2ef08109) removed Snapcraft's SIGUSR1-ignore workaround after Multipass fixed the underlying bug upstream in canonical/multipass#221. | |
| #2385 cli: consolidate re-execution | snapcraft | merged | Merged PR #2385 in commit 404255671, consolidating CLI re-execution under one console_scripts entry and leaving root handling to Multipass build-provider APIs. | |
| #2293 build providers: use the new snapcraft: remote for multipass | snapcraft | merged | Merged PR #2293 as commit 66060e839, switching Multipass builds to the snapcraft: remote and delegating unsupported-base errors to Multipass. | |
| #3275 cli: ignore sudo warning when using multipass | snapcraft | merged | Merged #3275 in commit cb23c00a5, suppressing Snapcraft's sudo warning when the Multipass build provider is used. | |
| #2869 build providers: use multipass from stable | snapcraft | merged | Merged in canonical/snapcraft#2869 (commit eb9bd8fbf), switching build providers to install Multipass 1.0 from the stable channel. |