Comment 2 for bug 1916552

Revision history for this message
Phillip Hernandez (samwiseg0) wrote :

- how snapcraft was invoked
It was invoked from a GitHub workflow found here.
https://github.com/sct/overseerr/actions/runs/561122420/workflow

- host system this was run on
The build were created using QEMU and Ubuntu 20.04 via GitHub

- version of snapd
2.49

- is this CI, are there CI build logs accessible?
Yes. The build logs can be found here.
https://github.com/sct/overseerr/runs/1887508955?check_suite_focus=true

After some further testing it seems to be an issue between the latest QEMU version and snapcraft.
After reverting to the previous QEMU version. The build process works again.
```
  - name: Set Up QEMU
        uses: docker/setup-qemu-action@v1
        with:
          image: tonistiigi/binfmt@sha256:df15403e06a03c2f461c1f7938b171fda34a5849eb63a70e2a2109ed5a778bde
```
I am not sure what QEMU may have changed that has caused an incompatibility with snapcraft/snapd and the latest version of QEMU.