Allow craft tools to function inside a LXD parent container when performing a LXD managed build
Metadata
Current evaluation
Enhancement request for craft tools to support nested LXD managed builds inside an LXD parent container. Maintainer linked UID/idmap work in craft-providers#259 and asked for workaround details; no response in 400 days.
Suggested action: close stale
Reason: Maintainer mr-cal asked on 2024-10-07 for the reporter's workarounds to determine whether this can be fixed in the outer LXD setup, and the author never responded after 400 days, leaving the enhancement unactionable.
Evaluated by: mr-cal-bot
Impact:
30
Quick Win:
2
Complexity:
75
Confidence:
75
Actionability:
20
Issue body
### What needs to get done
Please refer to this: https://ubuntu.com/blog/nested-containers-in-lxd
Currently when using spread with a LXD backend, running a craft tool does not appear to be supported using a nested LXD managed build backend. If this is actually supported, then this request is not needed ?
Supporting nested LXD instances in unprivileged containers require both the LXD parent and the LXD child container to have some agreements with regards to idmap ranges.
This feels like a great feature than can be solved inside the common craft libraries, with a documented requirement for the LXD parent container to support this usage case.
Here are some resources on the topic:
https://documentation.ubuntu.com/lxd/en/latest/userns-idmap/
### Why it needs to get done
This would expand the places where craft tools would "just work" without requiring provider specific tweaks. One use case is Spread LXD backend running craft tools suing managed builds.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| ~deepseek/deepseek-pro-latest |
Impact:
30
Quick Win:
2
Complexity:
75
Confidence:
75
Actionability:
20
|
close stale | Enhancement request for craft tools to support nested LXD managed builds inside an LXD parent container. Maintainer linked UID/idmap work in craft-providers#259 and asked for workaround details; no response in 400 days. | |
| stealth/space-bunny-alpha |
Impact:
41
Quick Win:
4
Complexity:
73
Confidence:
84
Actionability:
34
|
close stale | Nested-LXD support for LXD/Spread managed builds remains unresolved; the maintainer linked UID mapping to craft-providers#259 and requested workaround details that remain unanswered. | |
| qwen/qwen3.6-35b-a3b |
Impact:
45
Quick Win:
7
Complexity:
60
Confidence:
75
Actionability:
40
|
keep open | Enhancement request to support nested LXD containers for craft tools, particularly for Spread LXD backend managed builds. Maintainer requested workarounds and linked to craft-providers#259. | |
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
16
Staleness:
75
Complexity:
65
Confidence:
78
Support Request:
10
|
close stale | Request to support nested LXD managed builds (craft tools in a LXD parent container, e.g. Spread LXD backend), needing idmap range agreement. Maintainer asked for workaround details in Oct 2024; no reporter response since. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
65
Confidence:
80
Support Request:
20
|
close stale | Enhancement request to support nested LXD instances in unprivileged containers for craft tools. Lacks UID mapping configuration. Maintainer requested workarounds 10 months ago with no response, leaving it unaddressed. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
60
Confidence:
60
Support Request:
30
|
close stale | Enhancement request to support nested LXD managed builds by configuring UID mappings for craft tools inside LXD parent containers. Inactive for over a year with no response to maintainer's request for workarounds. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-providers#259
(confidence 90%)
Maintainer explicitly linked this issue as sharing UID configuration underpinnings.
Related issues
No related issues found above the similarity threshold.