Support the LXD provider
Metadata
Current evaluation
Feature request to add an LXD provider to imagecraft for parity with other crafts. Triaged and actively discussed; plan shifted to an LXD VM provider after FUSE/ublk/nbd workarounds were ruled out.
Suggested action: keep open
Reason: The issue is labelled 'Status: Triaged' and has an active maintainer discussion with a concrete plan (LXD VM provider per steinbro's 2026-05-20 comment). It remains blocked on external work — canonical/lxd#16070 and a craft-providers LXD VM provider — and the implementation path is still being researched, so it should stay open rather than be closed.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| ~deepseek/deepseek-pro-latest |
Impact:
55
Quick Win:
6
Complexity:
80
Confidence:
72
Actionability:
55
|
keep open | Feature request to add an LXD provider to imagecraft for parity with other crafts. Triaged and actively discussed; plan shifted to an LXD VM provider after FUSE/ublk/nbd workarounds were ruled out. | |
| qwen/qwen3.6-35b-a3b |
Impact:
50
Quick Win:
12
Complexity:
60
Confidence:
75
Actionability:
60
|
keep open | Feature request to add LXD provider support to Imagecraft. Triaged and actively discussed, with a current plan to use an LXD VM provider. Blocked by external LXD dependency (canonical/lxd#16070) and container block device limitations. | |
| qwen/qwen3.8-27b |
Impact:
65
Quick Win:
13
Staleness:
45
Complexity:
80
Confidence:
85
Support Request:
5
|
keep open | Feature request to add LXD provider support to Imagecraft. Triaged and actively discussed by maintainers with a current plan to use an LXD VM provider. Blocked by external LXD dependency (canonical/lxd#16070) and container block device limitations. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
45
Complexity:
75
Confidence:
90
Support Request:
10
|
keep open | Feature request to add LXD provider support to Imagecraft. Currently triaged and under technical discussion regarding workarounds for container block device limitations, pending external LXD functionality or VM provider implementation. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
20
Complexity:
80
Confidence:
90
Support Request:
10
|
keep open | Feature request to add LXD provider support to Imagecraft. Currently blocked by external LXD limitations and technical research into block device workarounds. Team is exploring an LXD VM provider approach and related unprivileged container improvements. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
20
Complexity:
75
Confidence:
90
Support Request:
10
|
keep open | Feature request to add LXD provider support for Imagecraft. Currently blocked by external LXD limitations and exploring workarounds like loopfs or VM providers. Maintainer triaged and actively discussing implementation paths. |
Update history
No update history recorded yet.
Related work
-
Blocked By:
craft-providers#895
(confidence 70%)
The planned LXD VM provider would need to be implemented in craft-providers, which imagecraft depends on for provider support.
-
Related To:
imagecraft#348
(confidence 65%)
mwhudson's comment references PR #348 ('No loops for grub') as a possible path to enable unprivileged container support.
-
Blocked By:
lxd#16070
(confidence 60%)
Issue body explicitly cites this LXD issue as the current blocker for container-based loop device support.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #895 Add a LXD VM provider | craft-providers | open | Add a VM-backed LXD provider for Imagecraft loop-device support; the requested capability remains open and is absent from the current provider tree. |