lxd: in is_user_permitted() check if connecting to LXD works
Metadata
Current evaluation
Merged #105 (commit 66797cb), replacing the hardcoded lxd-group check with a socket-writability check so custom LXD daemon groups work.
Resolution: closed resolved
Reason: PR #105 was merged, with resolving commit 66797cb and merge commit e58cc1b. The change makes is_user_permitted() verify LXD socket access instead of assuming membership in the lxd group.
Evaluated by: mr-cal-bot
No scores available.
Issue body
LXD doesn't always run as the `lxd` group as that is changeable
by the user (`snap set lxd daemon.group=adm`). As such, it is
better to check the socket to be writeable instead of hardcoding
a group.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #105 (commit 66797cb), replacing the hardcoded lxd-group check with a socket-writability check so custom LXD daemon groups work. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | Merged PR improving LXD permission check to verify socket writability instead of hardcoding the `lxd` group, supporting custom daemon group configurations. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #69 lxd: ensure user is permitted to use lxd (CRAFT-374) | craft-providers | merged | Merged PR #69 added LXD permission and readiness checks, resolving CRAFT-374 in commit 5478f63. | |
| #777 fix: check lxd availability for non-snap socket path | craft-providers | merged | Merged PR #777 via commit cf501cd, adding /var/lib/lxd/unix.socket as the first LXD permission check while retaining the Snap socket fallback. |