Container destroyed on snapcraft clean -s pull
Metadata
Current evaluation
Closed without resolution. The container destruction during snapcraft clean -s pull remains unaddressed and appears abandoned due to inactivity and zero discussion.
Suggested action: —
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 |
|---|---|---|---|---|
| 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
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. | |
| #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. | |
| #1774015 Cleaning breaks tried snap | snapcraft (launchpad) | closed | Closed without resolution. The snapcraft CLI and snapd disconnect causing snapcraft clean to break snap try states remains unfixed due to inactivity. | |
| #1615764 Support snapcraft close | snapcraft (launchpad) | closed | The requested snapcraft close command was closed without implementation. It appears abandoned due to prolonged inactivity, with zero comments or development activity after opening. |