Project mount in instance may use wrong uid
Metadata
Current evaluation
Project-mount UID handling was resolved upstream by canonical/craft-providers#98, enabling host-mount UID mapping instead of assuming the running user's UID.
Resolution: closed resolved
Reason: canonical/craft-providers#98 fixed the underlying UID mapping behavior, allowing Charmcraft mounts to use the project directory owner's UID and avoid unintended read-only mounts.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Charmcraft needs to specify the uid of the owner of the project directory when launching a craft-providers instance to prevent read-only mounts of the project dir when the currently running user and project dir owner are different. This was fixed in craft-providers in canonical/craft-providers#98.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Project-mount UID handling was resolved upstream by canonical/craft-providers#98, enabling host-mount UID mapping instead of assuming the running user's UID. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved upstream by canonical/craft-providers#98, which added caller-supplied host UID mapping so project mounts use the project directory owner's UID. | |
| stealth/space-bunny-alpha | — | closed resolved | Wrong project-mount UID was resolved upstream by craft-providers#98, which allowed applications to supply the host-mount UID mapping instead of using the running user's UID. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved via upstream fix in craft-providers. The project mount UID mismatch was addressed in canonical/craft-providers#98, ensuring correct ownership mapping during instance launches. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed by specifying the project directory owner UID during instance launch. The resolution was implemented upstream in craft-providers via canonical/craft-providers#98, preventing read-only mount issues. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed in canonical/craft-providers#98. Charmcraft now specifies the project directory owner's UID when launching instances, preventing read-only mounts when the running user differs from the directory owner. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-providers#98
(confidence 98%)
The issue explicitly identifies this upstream craft-providers PR as the fix.
Related issues
No related issues found above the similarity threshold.