← Back to issue list

Snapcraft should copy its config when running in SNAPCRAFT_BUILD_ENVIRONMENT=lxd

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1801155
Type
issue
State
closed
Author
~brlin
Labels
Created
Updated
Closed

Current evaluation

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

Snapcraft failing to copy cli.cfg to LXD build environments was closed without comments or resolution, indicating the request was abandoned. No fix was implemented.

Suggested action:

No scores available.

Issue body

I have set the following config in the cli.cfg ``` [Lifecycle] outdated_step_action = clean ``` but it won't work in the LXD build environment, IMO snapcraft should copy it before running the build.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Snapcraft failing to copy cli.cfg to LXD build environments was closed without comments or resolution, indicating the request was abandoned. No fix was implemented.
qwen/qwen3.6-35b-a3b Abandoned and closed without resolution or comments. No fix was implemented to automatically copy CLI configurations into the LXD build environment.
qwen3.6-35b-a3b-mtp-q6 Closed without resolution. The request to copy CLI configuration to the LXD build environment was abandoned due to prolonged inactivity.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#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%
#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.
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%
#1859469 snapcraft lxd + snapd transition in progress snapcraft (launchpad) closed Closed as non-reproducible and abandoned. The snapcraft lxd command failed due to a snapd transition conflict, but the issue was resolved in version 3.8 and later.
72%
#1890965 snapcraft --use-lxd is broken snapcraft (launchpad) closed Closed without a documented fix. The hardcoded LXD image URL returning 404 broke CI. Likely abandoned or resolved upstream.
72%
#1703344 snapcraft cleanbuild exits with a traceback when lxd is not installed snapcraft (launchpad) closed Closed without resolution. Missing LXD caused a FileNotFoundError during snapcraft cleanbuild. No comments, fixes, or status updates were provided.
72%
#1866300 snapcraft fails to build core20 snap snapcraft (launchpad) closed Closed without comments or resolution after 74 days. The core20 build failure involving multipass hangs and LXD tracebacks was abandoned.
71%
#1896820 Snapcraft can't be run against a local or remote LXD project snapcraft (launchpad) open Feature request from the LXD maintainer for snapcraft to support LXD projects (local/remote) for isolated or cluster-based builds. ~6 years old, no labels, zero comments, no maintainer response. Overlaps with remote LXD work tracked in snapcraft#4454.
71%
#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.
70%