← Back to issue list

Improve the LXD init experience

View original Github issue

Metadata

Project
rockcraft
Number
#590
Type
issue
State
open
Author
sergiusens
Labels
—
Created
Updated
Closed
—

Current evaluation

LXD init check for rockcraft pack is implemented in craft-providers. Maintainer kept issue open for two follow-ups: handling broken LXD profiles from older versions (PR #588 closed unmerged) and multi-profile selection. Inactive ~12.5 months.

Suggested action: keep open

Reason: Maintainer cjdcordeiro explicitly triaged and acknowledged the issue ('This is already in, but we can consider keeping this issue open for a bit longer'), identifying two valid follow-ups. The core LXD init check is confirmed in craft-providers code (is_initialized in installer.py, commit eda59e9). PR #588 to handle broken profiles was closed without merging, so that corner case remains unaddressed. The issue is triaged and still relevant, though low priority.

Impact: 25 Quick Win: 15.0 Staleness: 55 Complexity: 40 Confidence: 75 Support Request: 10

Issue body

### Bug Description e.g. no lxd init, rockcraft pack, failed with a cryptic message, did lxd init, rockcraft pack again rockcraft should check if LXD is properly installed and configured PO for LXD says there’s an easy way to check for this ### To Reproduce start from clean system ### Environment Ubuntu 24.04 fresh ### rockcraft.yaml ```shell . ``` ### Relevant log output ```shell . ```

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 25
Quick Win: 15.0
Staleness: 55
Complexity: 40
Confidence: 75
Support Request: 10
keep open LXD init check for rockcraft pack is implemented in craft-providers. Maintainer kept issue open for two follow-ups: handling broken LXD profiles from older versions (PR #588 closed unmerged) and multi-profile selection. Inactive ~12.5 months.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 40
Confidence: 75
Support Request: 20
keep open Feature request to improve LXD initialization checks in Rockcraft. Core implementation is complete, but maintainers noted open follow-ups for handling broken LXD profiles and multi-profile selection. Currently inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 80
Support Request: 0
close stale Request to improve LXD initialization checks in Rockcraft. Core functionality appears implemented, but follow-up enhancements for legacy broken profiles were discussed. Last active 10 months ago with no concrete next steps.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 50
Confidence: 75
Support Request: 15
close stale Rockcraft should verify LXD is initialized before building. Core check is implemented, but discussion remains on handling legacy broken profiles and profile selection. Open for ~2 years with recent maintainer comments.
qwen3.6-35b-a3b-mtp-q6
Staleness: 80
Complexity: 30
Confidence: 85
Support Request: 10
close stale Validates LXD setup in Rockcraft to prevent cryptic build failures. Core checks are implemented. Discussion continues on handling legacy broken profiles and adding profile selection. A related PR addresses the legacy profile issue.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/craft-providers#436 (confidence 80%)

    Commit eda59e9 'fix: require disk device in default lxd profile' added the is_initialized check that validates LXD default profile has a disk device at /, addressing the core 'cryptic message' complaint.

  • Related To: canonical/craft-providers#588 (confidence 70%)

    PR referenced by tigarmo to handle ill-formed LXD profiles from older rockcraft versions (follow-up point 1). Closed without merging, so the broken-profile deadlock remains unaddressed.

Related issues

Issue Project State Summary Similarity
#588 fix: handle ill-formed profiles created by older rockcraft craft-providers closed Adds a check for ill-formed LXD profiles from older rockcraft versions, prompting users to delete the project and retry. Currently pending review with 6 unresolved comments and no maintainer engagement for over 228 days.
78%
#213 Use alternate lxd profiles craft-providers open Enhancement request to add CRAFT_PROVIDERS_LXD_PROFILE env var for alternate LXD profiles. Open 3.5 years with one maintainer comment, no implementation.
74%
#684 Create a generic craft LXD profile craft-providers open Enhancement to create a generic craft LXD profile to protect managed containers from user-specific profile modifications affecting build reproducibility. Open 694 days with no maintainer response.
72%