Rootless build container

[pktpls]

Podman runs rootless and without a daemon in the background. Read about the dependencies here: https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md

• --userns=keep-id and the Z volume option make sure that permissions on shared filesystem resources (build_feed and the output directory) work alright between container and host.
• Logging verbosity is increased via bash set -ex and buildroot V=s. A human only ever reads this script's output when an automated build has failed, in which case they want a certain level of detail.
• In turn, a ton of warning noise is removed from the output. These are warnings from OpenWrt that aren't actionable for us.
• -j8 on make doesn't have any effect in our case.

The script eventually fails at make package/index for lack of a signing key, which is a separate issue I guess. A key could easily be placed at ./build-key and then be accessible at /home/build/repobuilder/build-key, which could be symlinked into the buildroot.

Tested on Fedora 36

[Akira25]

With the mentioned adjustments made, the script didn't produce package on a buildbot-worker. The Output-Dir was empty.

Maybe it helps for debugging: Buildbot calls the script with a command of this form.

./build_all_targets 'src-git falter https://github.com/freifunk-berlin/falter-packages^3e9a88bf3ab9c3c991e5a4f8b5278996d1ca6b15' /tmp/builder_test/ build_parallel

[pktpls]

Should be good now - but will it work on the buildbot workers? Are they standardized containers/vms?

[Akira25]

Should be good now - but will it work on the buildbot workers? Are they standardized containers/vms?

Buildbot-workers are simple debian-vms, which are handled by this role:
https://github.com/freifunk-berlin/ansible/tree/main/roles/buildbot_worker