← Back to issue list

Support LXD backend on non-Linux hosts

View original Github issue

Metadata

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

Current evaluation

Maintainer-authored enhancement to use the LXD provider on non-Linux hosts through a configured remote or VM. Remote arguments exist, but availability checks still require local LXD.

Suggested action: keep open

Reason: The maintainer-authored Type: Enhancement issue has a clear goal, and current code confirms partial support plus a real gap: LXDProvider exposes lxd_remote, while install(), is_installed(), is_user_permitted(), and LXD.version() still assume a local Linux daemon or socket. Keep it open for cross-platform readiness, version semantics, and tests; the broad scope needs design work rather than a mechanical change.

Evaluated by: mr-cal-bot

Impact: 57 Quick Win: 12 Complexity: 66 Confidence: 92 Actionability: 64

Issue body

### What needs to get done Non-Linux hosts should support the LXD backend by connecting to a LXD remote. That remote could be a remote LXD instance or a local VM running LXD. ### Why it needs to get done This would be much lighter weight than launching a multipass VM for each build.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 57
Quick Win: 12
Complexity: 66
Confidence: 92
Actionability: 64
keep open Maintainer-authored enhancement to use the LXD provider on non-Linux hosts through a configured remote or VM. Remote arguments exist, but availability checks still require local LXD.
stealth/space-bunny-alpha
Impact: 55
Quick Win: 15
Complexity: 60
Confidence: 86
Actionability: 68
keep open Open enhancement to let non-Linux hosts use configured LXD remotes, avoiding a heavyweight Multipass VM for each build.
stealth/space-bunny-alpha
Impact: 56
Quick Win: 14
Complexity: 61
Confidence: 72
Actionability: 66
keep open Enhancement to use the LXD provider on non-Linux hosts by connecting to a remote LXD instance or VM rather than launching a Multipass VM.
qwen3.6-35b-a3b-mtp-q6
Impact: 60
Quick Win: 18
Staleness: 75
Complexity: 70
Confidence: 65
Support Request: 10
needs triage Enhancement request to support LXD backend on non-Linux hosts via remote LXD connections. Untriaged, no maintainer response after 263 days.
qwen/qwen3.6-35b-a3b
Staleness: 50
Complexity: 50
Confidence: 85
Support Request: 5
needs triage Enhancement to enable LXD backend on non-Linux hosts by connecting to a remote LXD instance. Currently unassigned with no maintainer comments or progress in over three months.
qwen3.6-35b-a3b-mtp-q6
Staleness: 65
Complexity: 45
Confidence: 85
Support Request: 0
needs triage Enhancement to allow LXD backend on non-Linux hosts by connecting to a remote LXD instance or VM, replacing heavier multipass VMs. Currently open with no maintainer comments or assignee.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/craft-providers#508 (confidence 96%)

    Narrower open macOS report of the same local-installation blocker for remote LXD builds.

  • Related To: canonical/snapcraft#4454 (confidence 90%)

    Downstream triaged request to use remote LXD instances from macOS and other non-Linux hosts.

Related issues

No related issues found above the similarity threshold.