Container destroyed on snapcraft clean -s pull
Metadata
Current evaluation
Fixed by snapcraft PR #1655, which corrected clean-step handling so cleaning the pull step no longer unnecessarily destroys the build container.
Resolution: closed resolved
Reason: The final maintainer comment identified PR #1655 as the follow-up fix after PR #1587 was merged without the requested None-versus-pull handling. That targeted correction resolved the container-destruction behavior reported here.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Destroying the container on a `snapcraft clean` may be debatably ok but destroying it on a `snapcraft clean -s pull`, specially after being instructed to do so with:
```
The 'pull' step of 'osm-ro' is out of date:
The 'python-packages' part property appears to have changed.
In order to continue, please clean that part's 'pull' step by running:
snapcraft clean osm-ro -s pull
```
Is just a major slow down on productivity, more so when running on slow networks.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by snapcraft PR #1655, which corrected clean-step handling so cleaning the pull step no longer unnecessarily destroys the build container. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #1655 (commit ed32603c7) fixed step-specific LXD cleanup, preserving the build container for clean -s pull and avoiding costly rebuilds. | |
| stealth/space-bunny-alpha | — | closed resolved | LXD cleanup was fixed by merged PR #1655: clean removes build containers, while clean -s pull preserves or recreates them, avoiding needless rebuilds. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The container destruction during snapcraft clean -s pull remains unaddressed and appears abandoned due to inactivity and zero discussion. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The maintainer reported that snapcraft clean -s pull destroys containers, causing productivity slowdowns. No discussion or fix was provided, and the issue was closed without resolution. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The container destruction behavior during snapcraft clean -s pull remains unchanged, indicating the report was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution due to inactivity. The snapcraft clean -s pull container destruction report was abandoned. No fix was implemented. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#1655
(confidence 95%)
Maintainer explicitly proposed PR #1655 to fix the reported clean-step behavior.
-
Related To:
snapcore/snapcraft#1587
(confidence 90%)
Earlier refactor was referenced as the attempted fix and was merged without the requested handling.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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). | |
| #1570706 Snapcraft cleanbuild command doesn't work | snapcraft (launchpad) | closed | Fixed by merged canonical/snapcraft PR #458 (f78b1e3a3), which corrected Cleanbuilder constructor arguments so snapcraft cleanbuild could initialize its container. | |
| #1372 cli: Containerbuild clean | snapcraft | merged | Merged #1372, adding a unit test and fixing full clean behavior for SNAPCRAFT_CONTAINER_BUILDS=1. | |
| #1746381 snapcraft cleanbuild shouldn't always delete container at end | snapcraft (launchpad) | closed | No fix was made: maintainers confirmed cleanbuild containers were disposable, recommended SNAPCRAFT_CONTAINER_BUILDS, and left the request for default failure shells unimplemented. | |
| #1578170 Your first snap: snapcraft clean needed before second snapcraft stage | snapcraft (launchpad) | closed | Fixed in canonical/snapcraft#4 by PRs #442–#448 (commits 1a6a21831, 80de92254, 6224553ae, da1411df0): snapcraft.yaml changes now dirty lifecycle steps, avoiding the required manual clean. | |
| #1561328 cleaning a step on a dir built with an old snapcraft doesn't mention that a full clean is needed too | snapcraft (launchpad) | closed | Closed by merged PR #421 (commit 6ade3431), which changed the step-clean error to suggest a full clean instead of re-running the step when state is missing from an older snapcraft build dir. |