clean is checking lxd remote
Metadata
Current evaluation
Snapcraft now initializes the LXD remote lazily, so clean no longer starts a container unnecessarily; fixed by snapcore/snapcraft#1916 (dd4404843).
Resolution: closed resolved
Reason: PR snapcore/snapcraft#1916 was merged as commit dd4404843, deferring LXD remote initialization until the container is actually needed.
Evaluated by: mr-cal-bot
No scores available.
Issue body
It appears that
SNAPCRAFT_CONTAINER_BUILDS=1 snapcraft clean
is checking the lxd remotes. Is that really necessary? On my test build, it causes the container to be brought up, just for a clean.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Snapcraft now initializes the LXD remote lazily, so clean no longer starts a container unnecessarily; fixed by snapcore/snapcraft#1916 (dd4404843). | |
| stealth/space-bunny-alpha | — | closed resolved | snapcraft clean probed the LXD remote, spinning up a container needlessly. Fixed by PR #1916 ("lxd: initialize remote lazily", commit dd4404843), merged to defer remote init until actually needed. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #1372 (commit 9536f7887), which added coverage and corrected full-clean behavior for container builds, avoiding unnecessary container startup. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by canonical/snapcraft#1916 (commit dd4404843), which lazily initializes the LXD remote so `snapcraft clean` no longer starts it unnecessarily. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without documented resolution or fix. The issue reported that snapcraft clean unnecessarily checks LXD remotes and starts containers. No comments or follow-up actions were recorded, indicating it was likely abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Unnecessary LXD remote checks during snapcraft clean were reported but the issue was closed without resolution or fix. No comments or pull requests were created. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as abandoned without resolution or comments. The unnecessary LXD remote check during snapcraft clean was not addressed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution or comments. The report noted snapcraft clean unnecessarily checks LXD remotes, causing unwanted container startup. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#1916
(confidence 99%)
Merged commit dd4404843 implements lazy LXD remote initialization.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1655 lxd: distinguish argless clean from clean -s pull | snapcraft | merged | Merged in snapcraft#1655 (ed32603c7), fixing LXD cleanup so bare clean removes build containers while clean -s pull preserves or recreates them. | |
| #1666735 snapcraft cleanbuild does not work with lxd installed via snap | snapcraft (launchpad) | closed | Fixed by merged canonical/snapcraft#1199 (commit 417989880), making cleanbuild LXD detection packaging-independent instead of relying on apt package metadata. | |
| #1958930 `snapcraft clean <part> --use-lxd` shouldn't wait for network | snapcraft (launchpad) | open | Part-specific `snapcraft clean --use-lxd` unnecessarily starts a network-configured LXD environment; a maintainer suggested using offline mode, but no fix is recorded. | |
| #1739 lxd: refresh remote container | snapcraft | merged | Merged #1739 as 2f9265f23, fixing snapcraft refresh to honor the LXD remote named by SNAPCRAFT_CONTAINER_BUILDS instead of using a local container. | |
| #1734145 snapcraft clean <part-name> destroys everything when using containers | snapcraft (launchpad) | closed | Fixed targeted container cleanup: `snapcraft clean <part>` no longer deletes the LXD container while other parts remain; merged in #1762 (dbce9a058). | |
| #1587 lifecycle: clean after deleting container | snapcraft | merged | Merged PR #1587 (commit daca4618b): LXD cleanup logic moved into lxd.py's clean() so `snapcraft clean` removes leftover build containers, addressing the forum-reported container-build clean issue. | |
| #1703344 snapcraft cleanbuild exits with a traceback when lxd is not installed | snapcraft (launchpad) | closed | Fixed cleanbuild’s traceback when LXD is absent by handling the missing lxc executable and reporting a clear error. Merged in snapcraft#1400. |