← Back to issue list

locally built snapcraft switches channels in the container

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1884576
Type
issue
State
closed
Author
~ken-vandine
Labels
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 comments or resolution, likely abandoned. The reporter noted that locally built snapcraft switched to the latest/candidate channel inside an LXD container, preventing local changes from being available for testing.

Suggested action:

No scores available.

Issue body

After building a snap of snapcraft locally and installing it on my host. I get this when building something using lxd: snapcraft 4.0.6+git5.gd7594dd1 installed "snapcraft" switched to the "latest/candidate" channel So my snapcraft change I'm attempting to test is not available in the container.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without comments or resolution, likely abandoned. The reporter noted that locally built snapcraft switched to the latest/candidate channel inside an LXD container, preventing local changes from being available for testing.
qwen/qwen3.6-35b-a3b Closed without resolution. The issue reported locally built snapcraft switching to the latest/candidate channel inside LXD containers, blocking local change testing. Likely abandoned or resolved in subsequent releases.
qwen3.6-35b-a3b-mtp-q6 Closed without resolution, likely abandoned. Locally built snapcraft incorrectly switched to the latest/candidate channel inside LXD containers, blocking local change testing. No comments or fixes were provided.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#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.
71%
#1998100 Randomly I get "failed to inject host's snap 'snapcraft' into target environment." errors snapcraft (launchpad) closed Closed without resolution, likely abandoned due to inactivity. The failure occurs randomly when snapcraft's auto-refresh blocks LXD environment injection. Retrying the build works around the issue. No fix or merge was applied.
70%
#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.
70%