← Back to issue list

SNAPCRAFT_SETUP_CORE=1 doesn't work for foreign architectures

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1674828
Type
issue
State
closed
Author
~ryeterrell
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.

SNAPCRAFT_SETUP_CORE=1 failing for foreign architectures during classic snap builds was closed without resolution. Zero comments and no fixes indicate the report was abandoned due to inactivity.

Suggested action:

No scores available.

Issue body

Trying to build a classic snap on an amd64 box for arm64: $ SNAPCRAFT_SETUP_CORE=1 snapcraft --target-arch=arm64 Setting target machine to 'arm64' Preparing to pull kubectl classic confinement requires the core snap to be installed. Install it by running `snap install core`.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b SNAPCRAFT_SETUP_CORE=1 failing for foreign architectures during classic snap builds was closed without resolution. Zero comments and no fixes indicate the report was abandoned due to inactivity.
qwen/qwen3.6-35b-a3b Abandoned and closed without resolution. The SNAPCRAFT_SETUP_CORE=1 environment variable remains unsupported for foreign architectures.
qwen3.6-35b-a3b-mtp-q6 Closed and abandoned. No comments or patches were provided to resolve the SNAPCRAFT_SETUP_CORE=1 foreign architecture build failure, leaving the issue unresolved.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1997752 base core20: wrong arch triplet snapcraft (launchpad) closed Closed without a fix or resolution, likely abandoned due to inactivity. The report indicated Snapcraft incorrectly sets SNAPCRAFT_ARCH_TRIPLET when building on a mismatched host architecture. No comments or patches were submitted.
76%
#1760857 SNAPCRAFT_IMAGE_INFO contains wrong architecture snapcraft (launchpad) closed Closed without a linked fix or comments, indicating abandonment. The bug stems from lxc image list returning multiple matches, causing incorrect architecture values in SNAPCRAFT_IMAGE_INFO.
72%
#1822265 SNAPCRAFT_BUILD_ENVIRONMENT_* change doesn't apply to existing VMs snapcraft (launchpad) closed Closed without resolution. SNAPCRAFT_BUILD_ENVIRONMENT_* changes failing to apply to existing VMs were left unaddressed with zero comments, indicating the report was abandoned or marked stale.
72%
#1973376 SNAPCRAFT_ARCH_TRIPLET not usable with core22 base snapcraft (launchpad) closed Closed without resolution. The report details a core22 build failure where snapcraft rejects SNAPCRAFT_ARCH_TRIPLET in layout mount points during packing. Core20 remains compatible.
72%
#1660302 foreign architecture builds doesn't work with classic snaps snapcraft (launchpad) open Cross-arch builds (--target-arch) of classic snaps fail because the build environment lacks the core snap. Reported 2016 against snapcraft 2.x; 0 comments, no maintainer response; codebase since fully rewritten.
71%
#1817288 snapcraft cleanbuild produces incorrect architecture snap snapcraft (launchpad) closed Abandoned and closed without resolution. The legacy mode cleanbuild multi-arch naming bug remains unfixed due to lack of activity and deprecation of legacy mode.
71%
#1628915 SNAPCRAFT_PART_INSTALL is not being replaced when called by the build tools snapcraft (launchpad) closed Closed without a documented fix. The report detailed SNAPCRAFT_PART_INSTALL expansion failing in build tools, causing nested install paths. With zero comments and no follow-up, the issue was likely abandoned or superseded by subsequent project changes.
71%