← 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

Closed as obsolete when core-based classic builds moved to base snaps; no foreign-architecture code fix was identified.

Resolution: closed stale

Reason: The only recorded maintainer response, from ~sergiusens on 2021-08-06, directed the reporter to migrate to base snaps. No resolving PR or commit is identified, and the reported core-snap workflow was deprecated.

Evaluated by: mr-cal-bot

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
stealth/space-bunny-alpha — closed stale Closed as obsolete when core-based classic builds moved to base snaps; no foreign-architecture code fix was identified.
stealth/space-bunny-alpha — closed not a bug Closed after a maintainer advised migrating classic snaps from core to bases; classic-with-bases support was merged in canonical/snapcraft#2261 (8096c17b3).
stealth/space-bunny-alpha — closed not a bug Legacy core-based classic builds were no longer supported; the maintainer directed users to migrate to base snaps instead of fixing cross-architecture setup.
stealth/space-bunny-alpha — closed stale Closed after prolonged inactivity without resolution; no fix or workaround was implemented for SNAPCRAFT_SETUP_CORE=1 with foreign architectures.
stealth/space-bunny-alpha — closed stale Closed without resolution after prolonged inactivity; foreign-architecture builds still failed despite SNAPCRAFT_SETUP_CORE=1, and no fix or workaround was recorded.
qwen/qwen3.6-35b-a3b — — Closed without resolution due to prolonged inactivity. SNAPCRAFT_SETUP_CORE=1 fails during foreign architecture builds, but no fix or workaround was implemented.
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

Date Change
created

Related work

  • Related To: snapcraft#1112 (confidence 90%)

    Commit 49b39ef9a introduced classic-confinement core setup.

  • Related To: snapcraft#1576 (confidence 85%)

    Commit 338278005 added SNAPCRAFT_SETUP_CORE support in Docker.

Related issues

Issue Project State Summary Similarity
#1862256 snapcraft should complain loudly when building base: core20 snap on i386 snapcraft (launchpad) closed Closed as superseded: improved architecture parsing rejects unsupported core20/i386 builds, making a dedicated check unnecessary; snapcraft#4392 improved this handling.
75%
#1973376 SNAPCRAFT_ARCH_TRIPLET not usable with core22 base snapcraft (launchpad) closed Closed without a code fix: core22 requires CRAFT_ARCH_TRIPLET instead of SNAPCRAFT_ARCH_TRIPLET; the reporter confirmed Snapcraft 7.0.2 builds successfully with the replacement.
74%
#1665081 building a classic snap does'nt remove /snap/core/current snapcraft (launchpad) closed Closed without a code fix; the maintainer clarified that SNAPCRAFT_SETUP_CLASSIC=1 is only intended for CI use.
73%