snapcraft cleanbuild shouldn't always delete container at end
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
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.
Suggested action: —
No scores available.
Issue body
Building a snap using 'snapcraft cleanbuild' at the end there was a problem getting the snap out of the container, covered by bug 1746380. However, snapcraft immediately then threw away the container meaning I couldn't recover the snap manually, nor debug the issue.
Snapping 'pyradio' /
Snapped pyradio_1.3.2_amd64.snap
error: open /var/lib/snapd/hostfs/home/alan/tmp/pyradio/pyradio_1.3.2_amd64.snap: permission denied
Stopping local:snapcraft-saltishly-unsurgical-blondell
Traceback (most recent call last):
File "/snap/snapcraft/1069/bin/snapcraft", line 11, in <module>
load_entry_point('snapcraft==2.38', 'console_scripts', 'snapcraft')()
Perhaps snapcraft shouldn't trash the container given a successful snap was made, it just couldn't be recovered from the container?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The request to retain the container after successful builds but failed extraction was abandoned. No fix or merge occurred. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Requesting snapcraft cleanbuild to preserve containers after build failures was closed without resolution. No fix was implemented, leaving the feature abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1734145 snapcraft clean <part-name> destroys everything when using containers | snapcraft (launchpad) | closed | Closed without documented fix or comments. The maintainer reported destructive behavior during container-based clean operations, but the issue was abandoned or superseded by subsequent Snapcraft updates. | |
| #1816042 snapcraft cleanbuild fails if container isn't fully ready | snapcraft (launchpad) | closed | The issue describing snapcraft cleanbuild failures when the container is not fully ready was closed. | |
| #1570706 Snapcraft cleanbuild command doesn't work | snapcraft (launchpad) | closed | Closed without resolution, likely abandoned or superseded. The cleanbuild command failed due to LXC hash format incompatibility and container stop errors. | |
| #1570708 snapcraft should remove lxd container once finished the build | snapcraft (launchpad) | closed | Requested automatic LXD container cleanup after snapcraft cleanbuild was closed without resolution. Zero comments and no implementation indicate the request was abandoned. | |
| #1746359 snapcraft cleanbuild --debug should provide guidance on build failure | snapcraft (launchpad) | closed | Closed as abandoned due to inactivity. The requested debug shell guidance for snapcraft cleanbuild was never implemented. | |
| #1609803 snapcraft cleanbuild --no-clean-up | snapcraft (launchpad) | closed | Feature request to add a --no-clean-up flag to snapcraft cleanbuild was closed without implementation. The issue appears abandoned or declined, with no comments or resolution details provided. | |
| #1729069 snapcraft container builds with snap try | snapcraft (launchpad) | closed | Abandoned. The container build cp error during snap try remains unfixed due to age and lack of developer activity. | |
| #1624075 cleanbuild - Don't try to stop a non-existent container | snapcraft (launchpad) | closed | Closed without resolution, likely abandoned. The report detailed snapcraft cleanbuild failing when attempting to stop a non-existent LXC container. | |
| #1583718 snapcraft command doesn't include expected changes | snapcraft (launchpad) | closed | Closed without resolution or comments. The build caching bug was abandoned or superseded by later improvements, requiring manual cache cleaning as a workaround. | |
| #1788654 snapcraft cleanbuild doesn't work with cross-compile stage-packages | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft cleanbuild fails during cross-compilation because it does not automatically configure multi-arch package support inside the container. No fix was implemented, and the report appears abandoned. |