How to build snap for non-amd64 architectures from GitHub

juliank · September 1, 2026, 3:13pm

Hi friends,

we are trying to figure out how to build the fwupd snap for the non-amd64 architectures.

To provide some context:

The snap is built from the fwupd/fwupd upstream repo directly at this point using a GitHub
But the snap is now owned by Canonical
We want to install the snap by default on Ubuntu 26.10 onward.

We’re trying to figure out the best practices to move forward here.

Lin-Buo-Ren · September 2, 2026, 5:08pm

Maybe this GitHub workflow will help?

github.com/snapcrafters/ci

release-to-candidate/README.md

main

# snapcrafters/ci/release-to-candidate

This action is used to run `snapcraft remote-build` for a given Snap, and a given architecture.
Following that, the snap is released to the specified channel automatically.

## Usage

```yaml
# ...
jobs:
  release:
    name: 🚢 Release to latest/candidate
    runs-on: ubuntu-latest
    steps:
      - name: 🚢 Release to latest/candidate
        uses: snapcrafters/ci/release-to-candidate@main
        with:
          architecture: arm64
          launchpad-token: ${{ secrets.LAUNCHPAD_TOKEN }}
          store-token: ${{ secrets.STORE_TOKEN }}

This file has been truncated. show original

See also:

dsteinbrook · September 2, 2026, 5:23pm

@Lin-Buo-Ren’s suggestion is a good one. I’d also recommend taking a look at the GitHub workflows for the crafts themselves (Snapcraft, Charmcraft, Rockcraft, etc.) which are similarly built and published as snaps for all officially-supported architectures. The main takeaway is that work is delegated to Launchpad infrastructure for s390x, ppc64el, etc.