S390x and ppc failing to build

snapcraft
1

Similar to Launchpad builds for amd64 & i386 fail: snapd snap install errors with "cannot set capabilities: Operation not permitted" I have a couple of snaps that no longer build on specific architectures.

I’m getting “cannot set privileged capabilities: Operation not permitted” in the log, then it dies. Previously worked fine, and other architectures are fine.

Restarting host AppArmor
Command output: b''
Command errors (if any): b''
Running build phase...
cannot set privileged capabilities: Operation not permitted
Build failed
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 323, in run
    self.build()
  File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 306, in build
    self.run_build_command(["snapcraft"], cwd=output_path, env=env)
  File "/usr/lib/python3/dist-packages/lpbuildd/target/operation.py", line 70, in run_build_command
    return self.backend.run(args, cwd=cwd, env=full_env, **kwargs)
  File "/usr/lib/python3/dist-packages/lpbuildd/target/lxd.py", line 736, in run
    subprocess.check_call(cmd, **kwargs)
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['lxc', 'exec', 'lp-noble-ppc64el', '--env', 'LANG=C.UTF-8', '--env', 'SHELL=/bin/sh', '--env', 'http_proxy=http://10.10.10.1:8222/', '--env', 'https_proxy=http://10.10.10.1:8222/', '--env', 'HTTP_PROXY=http://10.10.10.1:8222/', '--env', 'HTTPS_PROXY=http://10.10.10.1:8222/', '--env', 'GIT_PROXY_COMMAND=/usr/local/bin/lpbuildd-git-proxy', '--env', 'SNAPPY_STORE_NO_CDN=1', '--env', 'LAUNCHPAD_INSTANCE=production', '--env', 'LAUNCHPAD_SERVER_URL=launchpad.net', '--env', 'SNAPCRAFT_BUILD_INFO=1', '--env', 'SNAPCRAFT_IMAGE_INFO={"build-request-id": "lp-104148296", "build-request-timestamp": "2025-12-12T19:02:05Z", "build_url": "https://launchpad.net/~build.snapcraft.io/+snap/3030e2553bf14ccbbc521999c9e23e96/+build/2989701"}', '--env', 'SNAPCRAFT_BUILD_ENVIRONMENT=host', '--env', 'SNAPCRAFT_BUILD_FOR=ppc64el', '--env', 'CRAFT_PLATFORM=ppc64el', '--', '/bin/sh', '-c', 'cd /build/syft && linux64 snapcraft']' returned non-zero exit status 1.
Revoking proxy token...
[Fri Dec 12 19:10:52 2025]
RUN: /usr/share/launchpad-buildd/bin/in-target scan-for-processes --backend=lxd --series=noble --abi-tag=ppc64el --isa-tag=ppc64el SNAPBUILD-2989701
Scanning for processes to kill in build SNAPBUILD-2989701

Bad log: https://launchpadlibrarian.net/837191174/buildlog_snap_ubuntu_noble_ppc64el_3030e2553bf14ccbbc521999c9e23e96_BUILDING.txt.gz

Good log: https://launchpadlibrarian.net/837191135/buildlog_snap_ubuntu_noble_arm64_3030e2553bf14ccbbc521999c9e23e96_BUILDING.txt.gz

1 Like
2

Also, see Launchpad builds for i386 fail: Command errors (if any): b''

1 Like
3

I just looked in Matrix, and an announcement was made there by Alex Lowe ( @lengau )

JSYK folks, any ppc64el or s390x snaps are going to fail to build right now due to a small fire at Launchpad. The workaround for the moment is to use the beta channel of snapd, but that doesn’t work for our remote build CI (see: chore: bump ruff to version 0.14.9 · snapcrafters/ruff@566cfcd · GitHub)

That and riscv64 builds taking longer than 6 hours and thus timing out have me wondering whether we could set up an alternative CI that uses snap recipes in Launchpad.

I’m happy to work on that, but I’d like to check whether that would be welcome and, if so, how I should architect it. If anyone has opinions LMK — I’d like to work on it during the last week of the year.