lxd: unset SNAP to work-around LXD deb thinking it's a snap
Metadata
Current evaluation
Rejected and closed. Maintainers declined the workaround, preferring a proper fix in LXD or a redesigned environment handler. The pull request was abandoned without merging despite ongoing user breakage.
Suggested action: —
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] If this is a bugfix. Have you checked that there is a bug report open for the issue you are trying to fix on [bug reports](https://bugs.launchpad.net/snapcraft)?
- [x] If this is a new feature. Have you discussed the design on the [forum](https://forum.snapcraft.io)?
- [x] Have you successfully run `./runtests.sh static`?
- [x] Have you successfully run `./runtests.sh unit`?
-----
Work-around for [LP: #1746612](https://bugs.launchpad.net/snapcraft/+bug/1746612)
Manual test steps:
1. Have LXD v2.21 deb installeed
2. `$ snapcraft cleanbuild`
3. Observe that the build succeeds
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Rejected and closed. Maintainers declined the workaround, preferring a proper fix in LXD or a redesigned environment handler. The pull request was abandoned without merging despite ongoing user breakage. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected and closed without merging. Maintainer opposed the workaround, preferring an upstream LXD fix or a redesigned handler. Despite contributor pushback regarding prolonged user impact, the PR was abandoned and never merged. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected by maintainers who preferred an upstream LXD fix or a redesigned run handler over a workaround. Despite contributor pushback regarding persistent user impact, the pull request was closed without merging. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1814928 Can't build a Snap program using lxd | snapcraft (launchpad) | closed | Closed without resolution. LXD containers cannot access the msr module required for Snap builds, rendering the guide unworkable. No fix or workaround was provided. | |
| #1568 lxd: don't re-inject the same snaps | snapcraft | merged | Merged a fix for an LXD bug that repeatedly re-injected identical snaps due to mismatched revision filenames. The change resolves the issue by comparing snap hashes instead of relying on filename matching, preventing unnecessary reinstallations. | |
| #1746612 Snapcraft cleanbuild doesn't work if you're not using the LXD snap | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft hardcodes the LXD snap path during cleanbuild, causing failures with deb-installed LXD. The report appears abandoned or superseded by updated Snapcraft versions that dynamically detect LXD installations. | |
| #1788667 changes in snapd break lxd snap injection for cleanbuild | snapcraft (launchpad) | closed | Abandoned. snapd permission changes to 0600 broke LXD snap injection for cleanbuild in unprivileged containers. No fix or workaround was implemented. | |
| #1577 lxd: don't inject local snaps on a different arch | snapcraft | merged | Merged a fix preventing Snapcraft from injecting local snaps into LXD containers with mismatched architectures. Cross-arch remotes now install snaps from the store. Approved by reviewers and merged after CI checks. | |
| #1639641 Don't assume lxd from dpkg | snapcraft (launchpad) | closed | Resolved via merged pull request #904, updating snapcraft cleanbuild to detect LXD installed via snap rather than only checking dpkg. |