snapcraft does not properly detect the architecture when kernel is 64 bits but userspace is 32
Metadata
Current evaluation
Closed without resolution. Snapcraft incorrectly identified arm64 architecture in 64-bit kernel/32-bit userspace chroots, generating mismatched snaps. The report was abandoned due to inactivity.
Suggested action: —
No scores available.
Issue body
Building a snap in a chroot in a phone that has 64 bits kernel but 32 bits user space produces a snap that is supposed to be 64 bits, with name *_arm64.snap and snap.yaml containing:
<<
architectures:
- arm64
>>
However, the compiled files are 32 bits, because:
$ gcc -v |& grep Target
Target: arm-linux-gnueabihf
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snapcraft incorrectly identified arm64 architecture in 64-bit kernel/32-bit userspace chroots, generating mismatched snaps. The report was abandoned due to inactivity. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. Snapcraft misdetected arm64 architecture on 64-bit kernel/32-bit userspace chroots, packaging 32-bit binaries with arm64 metadata. Closed without resolution or follow-up. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5638 Snapcraft fails to run on 32bit userspace container on 64bit ARM kernel. | snapcraft | closed | Closed and moved to internal tracking (SNAPCRAFT-1190). No fix merged; the proposed architecture mapping remains unimplemented. | |
| #1520248 snap with only scripts gets wrongs architecture set | snapcraft (launchpad) | closed | Closed without comments or resolution. Snapcraft 0.5 incorrectly flagged script-only snaps as missing amd64 binaries. The issue was abandoned and likely resolved in later snapcraft versions. | |
| #1570835 snapcraft 2.8 fails on s390x | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft 2.8 failed on s390x due to a missing architecture table entry, but no fix or follow-up was recorded. | |
| #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. | |
| #5219 Snapcraft unable to compile ARM64 kernel | snapcraft | open | Cross-compiling an ARM64 kernel with snapcraft 7.5.8/8.5.1 fails when the kernel plugin runs 'apt-get download snapd:arm64' for snap bootstrap, because the Focal build environment has no snapd arm64 candidate. No maintainer response; reporter reproduced the apt error on Ubuntu 20/22 in Jan 2025. | |
| #4627 Cannot build snaps in a 32-bit armhf container when running an arm64 kernel | snapcraft | closed | Closed without a public fix. An internal Jira ticket (CRAFT-2567) was created to track the architecture detection error, but no resolution or update was provided, leaving the issue deferred. | |
| #1980536 snapcraft unusable on systems not using apt | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft retained hard apt dependencies, causing crashes on non-Debian systems like Arch Linux. The issue appears abandoned with no fix provided. | |
| #1907721 Snapcraft broken on ARM64 | snapcraft (launchpad) | closed | Closed without comments. No fix or merge was applied. The ARM64 Multipass QEMU error and YAML !PrimeState deserialization bug were likely resolved by upstream Snapcraft updates or abandoned. | |
| #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. | |
| #2015091 snapcraft download debian package from incorrect arch | snapcraft (launchpad) | open | Cross-architecture gadget snap downloads wrong arch deb (amd64 instead of arm64). Issue is 1249 days old with no maintainer engagement, labels, or assignee. |