← Back to issue list

cleanbuild - Don't try to stop a non-existent container

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1624075
Type
issue
State
closed
Author
~joetalbott
Labels
cleanbuild
Created
Updated
Closed

Current evaluation

⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.

Closed without resolution, likely abandoned. The report detailed snapcraft cleanbuild failing when attempting to stop a non-existent LXC container.

Suggested action:

No scores available.

Issue body

josepht@spruce:~/src/bzr/nmap-ubuntu-core/current_work$ snapcraft cleanbuild "confinement" property not specified: defaulting to "strict" "grade" property not specified: defaulting to "stable" error: not found (not a fingerprint, partial fingerprint (first 12 chars) or valid alias) Stopping snapcraft-mainly-handy-cod error: not found Command '['lxc', 'stop', '-f', 'snapcraft-mainly-handy-cod']' returned non-zero exit status 1

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without resolution, likely abandoned. The report detailed snapcraft cleanbuild failing when attempting to stop a non-existent LXC container.
qwen/qwen3.6-35b-a3b Fixed by adding a pre-check to skip stopping non-existent LXC containers during snapcraft cleanbuild, resolving the exit status 1 error.
qwen3.6-35b-a3b-mtp-q6 Resolved by modifying snapcraft to skip stopping non-existent LXC containers during cleanbuild, preventing the command failure. Closed without further comments.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#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.
76%
#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.
76%
#1675516 can't cleanbuild snapcraft itself snapcraft (launchpad) closed Closed without resolution or comments, the report of a failed snapcraft cleanbuild due to missing build-packages was abandoned.
74%
#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.
74%
#1719952 When cleanbuild starts, the container has no connection and prints an ugly error snapcraft (launchpad) closed Abandoned due to inactivity. The report described misleading network error tracebacks during snapcraft cleanbuild startup before container connectivity. No fix or discussion was provided.
73%
#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.
73%
#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.
72%
#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.
71%
#1685820 cleanbuild doesn't work in distros without /etc/apt/apt.conf.d/ snapcraft (launchpad) closed Closed without resolution. The cleanbuild command failed on non-Debian distros due to missing apt configuration. The feature was subsequently abandoned as Snapcraft deprecated LXD-based cleanbuild and shifted to cloud builders.
70%
#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.
70%