snapcraft should remove lxd container once finished the build
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Requested automatic LXD container cleanup after snapcraft cleanbuild was closed without resolution. Zero comments and no implementation indicate the request was abandoned.
Suggested action: —
No scores available.
Issue body
Currently snapcraft polutes the system with container instances when using the snapcraft cleanbuild command. It should delete an instance once its done using it.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Requested automatic LXD container cleanup after snapcraft cleanbuild was closed without resolution. Zero comments and no implementation indicate the request was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without fix. The request to automatically remove LXD containers after snapcraft cleanbuild builds was abandoned due to inactivity. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed due to inactivity. The feature request to automatically remove LXD containers after snapcraft cleanbuild was abandoned without implementation or resolution. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1666735 snapcraft cleanbuild does not work with lxd installed via snap | snapcraft (launchpad) | closed | Closed without resolution or merge. The report notes snapcraft cleanbuild fails to detect LXD installed via snap, suggesting checks via snap list or lxc list instead of apt cache. No fix was implemented or documented. | |
| #1752498 cleanbuild fails with lxd snap | snapcraft (launchpad) | closed | A user reported snapcraft cleanbuild failing with the LXD snap due to a FUSE mount permission error inside the container. With zero comments and years of inactivity, the report was abandoned and closed without a fix or resolution. | |
| #1456 clean up stale containers | snapcraft | closed | Closed without implementation. Links to an external design discussion for cleaning up stale LXD containers created by snapcraft. No code changes were applied, indicating the request was abandoned or deferred pending design decisions. | |
| #1746381 snapcraft cleanbuild shouldn't always delete container at end | snapcraft (launchpad) | closed | Closed without implementation. The request to preserve the container after a successful build for debugging was not addressed, likely abandoned or superseded by newer workflows. | |
| #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. | |
| #1697979 snapcraft fails on initial cleanbuild probe | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft cleanbuild failed due to LXD connection errors when LXD was provided via a third-party snap alias. The report received no comments or fixes and was abandoned. | |
| #1839399 snapcraft not pulling snap from lxd container | snapcraft (launchpad) | open | 2019 report that snapcraft 3.7.1 with --use-lxd built a snap inside the LXD container but never copied it back to the host. No labels, no maintainer interaction, 7 years old; the LXD provider has since been rewritten via craft-providers. | |
| #1480144 cleanbuild (through lxd) | snapcraft (launchpad) | closed | Closed as a wishlist item. The request to integrate snapcraft with clean build environments like cowbuilder or LXD was abandoned due to lack of priority and activity. | |
| #1434 lxd: clean with no parts should only delete | snapcraft | merged | Merged. Updates snapcraft LXD handling so running clean without arguments only deletes container resources instead of executing commands inside them. Approved by one reviewer and merged. | |
| #1700703 container builds fail after creating the container | snapcraft (launchpad) | closed | Closed without comments or resolution. The LXD id mapping failure during snapcraft container builds was likely abandoned or superseded by newer container build implementations. |