← Back to issue list

Use alternate lxd profiles

View original Github issue

Metadata

Project
craft-providers
Number
#213
Type
issue
State
open
Author
cmatsuoka
Labels
Type: Enhancement
Created
Updated
Closed
—

Current evaluation

Enhancement request (by maintainer cmatsuoka) to allow alternate LXD profiles, e.g. CRAFT_PROVIDERS_LXD_PROFILE(S), for devs with multiple pools. mr-cal replied with design questions (plural list, global vs per-app) still unanswered; no code implements profiles.

Suggested action: keep open

Reason: The request remains unimplemented: project.py's create_with_default_profile still defaults to profile="default" and launcher.py:295 calls it without a profile argument, and a pickaxe search for 'CRAFT_PROVIDERS_LXD' found no commits, so there is nothing to close as resolved. It has been triaged (labelled 'Type: Enhancement' and mr-cal replied 'Great suggestion! I added some thoughts'), so it is not untriaged, but mr-cal's own questions — whether the variable should be plural/comma-separated and whether profiles are global to craft-providers or passed per craft application via SNAPCRAFT_LXD_PROFILES etc. — were never answered, which is why actionability is only mid-range. Age alone is not grounds for closure; the feature is still valid for users running multiple LXD pools.

Evaluated by: mr-cal-bot

Impact: 38 Quick Win: 9 Complexity: 45 Confidence: 72 Actionability: 45

Issue body

I have multiple lxd pools and I'd like to have some mechanism in craft-providers that allows me to use alternate lxd profiles during development so I can use different pools with different configurations. An environment variable such as `CRAFT_PROVIDERS_LXD_PROFILE` specifying the profile to use would solve my problem.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 38
Quick Win: 9
Complexity: 45
Confidence: 72
Actionability: 45
keep open Enhancement request (by maintainer cmatsuoka) to allow alternate LXD profiles, e.g. CRAFT_PROVIDERS_LXD_PROFILE(S), for devs with multiple pools. mr-cal replied with design questions (plural list, global vs per-app) still unanswered; no code implements profiles.
stealth/space-bunny-alpha
Impact: 45
Quick Win: 12
Complexity: 55
Confidence: 82
Actionability: 58
keep open Requests configurable alternate LXD profiles for different pools; acknowledged, but implementation scope remains unresolved.
qwen3.6-35b-a3b-mtp-q6
Impact: 50
Quick Win: 30
Staleness: 75
Complexity: 40
Confidence: 65
Support Request: 10
needs triage Enhancement request to add CRAFT_PROVIDERS_LXD_PROFILE env var for alternate LXD profiles. Open 3.5 years with one maintainer comment, no implementation.
qwen/qwen3.6-35b-a3b
Staleness: 70
Complexity: 45
Confidence: 80
Support Request: 10
keep open Request to add an environment variable for specifying alternate LXD profiles in craft-providers. Maintainer discussed implementation scope and naming, but no progress has been made in over three years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 20
Confidence: 65
Support Request: 0
keep open Request to add an environment variable for specifying alternate LXD profiles in craft-providers. Maintainer discussed implementation details and alternative approaches, but no decision or implementation has been made.

Update history

No update history recorded yet.

Related work

  • Related To: craft-providers#436 (confidence 55%)

    Commit eda59e9 'fix: require disk device in default lxd profile (#436)' and installer.is_initialized hardcode profile="default"; adding profile support would need to relax that assumption.

Related issues

Issue Project State Summary Similarity
#684 Create a generic craft LXD profile craft-providers open A dedicated craft LXD profile is proposed to isolate build containers from user-edited defaults; the open enhancement still needs a decision on shared versus per-user profiles.
75%