← Back to issue list

snapcraft cleanbuild fails if container isn't fully ready

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1816042
Type
issue
State
closed
Author
~popey
Labels
—
Created
Updated
Closed

Current evaluation

Closed as obsolete: @sergiusens said cleanbuild was no longer supported because normal builds now transparently provide clean builds.

Resolution: closed stale

Reason: No container-readiness fix was recorded. @sergiusens closed the report on 2023-08-17, noting that the standalone cleanbuild command had been decommissioned and clean builds were now the default.

Evaluated by: mr-cal-bot

No scores available.

Issue body

I'm using cleanbuild to build some non-base legacy applications. Unfortunately on my home microserver (which isn't super fast) I can often find that snapcraft fails to be installed inside the container and thus the application is unable to be built.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed stale Closed as obsolete: @sergiusens said cleanbuild was no longer supported because normal builds now transparently provide clean builds.
stealth/space-bunny-alpha — closed stale Cleanbuild’s container-readiness failure was left unfixed; the standalone command was deprecated because builds now use clean environments by default.
stealth/space-bunny-alpha — closed stale Reported cleanbuild failures installing Snapcraft inside slow containers; closed without a recorded fix, linked PR, or maintainer explanation after prolonged inactivity.
qwen/qwen3.6-35b-a3b — — Abandoned and closed without resolution. The report detailed snapcraft cleanbuild failures on slower hardware caused by container readiness timeouts. No comments, patches, or workarounds were provided.
qwen/qwen3.6-35b-a3b — — The issue describing snapcraft cleanbuild failures when the container is not fully ready was closed.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The snapcraft cleanbuild container readiness failure was abandoned due to prolonged inactivity, with no fix or workaround implemented.
qwen3.6-35b-a3b-mtp-q6 — — Abandoned. Snapcraft cleanbuild failed when containers were not fully ready on slower hardware, but no fix or resolution was provided.

Update history

Date Change
created

Related issues

Issue Project State Summary Similarity
#1697979 snapcraft fails on initial cleanbuild probe snapcraft (launchpad) closed Closed as obsolete: cleanbuild was decommissioned, and standard Snapcraft builds now transparently use a clean build environment.
82%
#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.
80%
#1800119 snapcraft cleanbuild snapcraft (launchpad) closed The obsolete cleanbuild command was retired because builds became clean by default; a maintainer closed the report in August 2023.
79%
#1746359 snapcraft cleanbuild --debug should provide guidance on build failure snapcraft (launchpad) closed Superseded by Snapcraft 3.x base-based build environments, which replaced the legacy cleanbuild --debug container workflow.
75%
#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.
75%
#1811208 snapcraft failed to build with cleanbuild on 18.04 snapcraft (launchpad) closed Expired after 60 days without activity; no fix was recorded. A maintainer advised using --destructive-mode because cross-compilation in build environments was unsupported.
74%
#1570708 snapcraft should remove lxd container once finished the build snapcraft (launchpad) closed Closed as invalid after PR #459 found cleanbuild already destroyed its LXD containers; a separate argument-passing failure was fixed by #458 (f78b1e3a3).
73%
#1788654 snapcraft cleanbuild doesn't work with cross-compile stage-packages snapcraft (launchpad) closed Closed as an obsolete legacy cleanbuild/LXD issue after a maintainer directed users to migrate to bases; no targeted cross-architecture fix was recorded.
73%
#1372 cli: Containerbuild clean snapcraft merged Merged #1372, adding a unit test and fixing full clean behavior for SNAPCRAFT_CONTAINER_BUILDS=1.
73%
#1752498 cleanbuild fails with lxd snap snapcraft (launchpad) closed Closed as obsolete: the cleanbuild command was removed; Snapcraft builds now perform clean builds by default.
72%