LXD config set raw.idmap random not applied
Metadata
Current evaluation
Fixed by merged PR #386, which corrected LXC instance locking during creation so raw.idmap is applied.
Resolution: closed resolved
Reason: PR canonical/craft-providers#386 was merged and fixed creation-time locking so the LXC configuration, including raw.idmap, is applied correctly.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
LXC return successl, but `raw.idmap` not set
### To Reproduce
N/A
### part yaml
_No response_
### Relevant log output
```shell
N/A
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #386, which corrected LXC instance locking during creation so raw.idmap is applied. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | Resolved in craft-providers#386 by fixing LXC instance locking during creation, addressing the raw.idmap application issue. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/craft-providers#386
(confidence 99%)
The merged PR changed instance creation to use only the instance-specific LXC lock.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #769 LXD idmap improperly set for high uids and gids | craft-providers | closed | Fixed by merged PR #98 (76a2d3a): LXD raw.idmap now maps the host UID and GID separately, correcting ownership for high, mismatched IDs. | |
| #1904 lxd: raw.idmap expects host and container id respectively | snapcraft | merged | Merged PR #1904 fixed LXD `raw.idmap` argument order so host UID maps to container root (0), instead of mapping both IDs to the host user; commit 6bd4c9e59. | |
| #1385 lxd: Don't assume user ID to 1000 for raw.idmap | snapcraft | merged | Merged PR #1385 as commit e85e0779b, removing LXD raw.idmap's hard-coded UID 1000 assumption for Launchpad bug 1700703; PR #1904 later corrected mapping order. |