ci: introduce px4-dev container with multi arch support

[mrpollo]

Use the px4-dev container to build and publish all targets

• builds x86, and arm64 px4-dev images
  • conditional to changes in either ubuntu.sh or requirements.txt
• updates ubuntu.sh for installing under both architectures
• fixes a stringop-overflow issue with gcc > 12
• uses the px4-dev container to build the build matrix of all boards

[alexcekay]

Hi @dagar and @mrpollo,
thanks for the effort 👍

Regarding the compiler errors you guys are facing. I had the same ones when trying to use the Noble containers I created in PX4.

• Dangling Pointers
• Stringop Overflow

I had a look at the relevant code and they are false positives. I solved it by ignoring the specific false positives in the relevant files.

For the Dangling Pointers:

• https://github.com/alexcekay/PX4-Autopilot/pull/19/files#diff-14c9866c1e51f3c9132cf332d39ed71f75562c0331b56a38006646d3ada30044
• https://github.com/alexcekay/PX4-Autopilot/pull/19/files#diff-d5cdc23c1c6e3b44595156b57ed0c46cafdf78109f53867da99e7cff66808b87
• https://github.com/alexcekay/PX4-Autopilot/pull/19/files#diff-273959302bcc3e28578f28dcac558e14eeac22e2f0489f8f37ed3225c81af8f6
• https://github.com/alexcekay/PX4-Autopilot/pull/19/files#diff-6a102239cfca73f98dc6349c1b7d969fb26f868be0e6e28ee53b7c0817bf6813

For Stringop Overflow:

• https://github.com/alexcekay/PX4-Autopilot/pull/19/files#diff-a9f91043ac9732c1ead9816674db6f806a64115a0c00e561d3f175a87747983f

Regarding the last failed run you posted: This seems like curl is not installed in the image.

[mrpollo]

thanks for the fix @alexcekay I pushed a commit to the libdronecan lib for the stringop-overflow error, however the remaining failures are not present anymore, hopefully it means they got fixed elsewhere!

[DronecodeBot]

This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there:

https://discuss.px4.io/t/px4-sync-q-a-mar-05-2025/44169/5

[DronecodeBot]

This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there:

https://discuss.px4.io/t/px4-sync-q-a-mar-26-2025/44527/1

[afwilkin]

@mrpollo The only thing that was an issue was the ESC calibration failing: #24022 (comment)

we will need to flash stable and 1.16 beta to narrow down the issue

It appears that this issue is not a toolchain change. It is presenting itself in 1.16-beta as well as 1.15.4 as well
#24645

[alexcekay]

Thanks for the testing @afwilkin, really helpful.
@mrpollo: Is there anything left to do regarding this PR?

[mrpollo]

yes, I'm working out how to build both container images in independent native runners so its faster, it just needs an last push, I just haven't had the time, I will however get to it this week

[mrpollo]

Finally managed to get the containers to work, here's the multi-arch builds published to both registries.

Next step is to make pushing to registry conditional to when we push a tag, this way we only have tagged containers going forward.

https://github.com/PX4/PX4-Autopilot/pkgs/container/px4-dev/398560804?tag=v1.16.0-beta1-147-g017b361eb7

https://hub.docker.com/repository/docker/px4io/px4-dev/tags/v1.16.0-beta1-147-g017b361eb7/sha256-5333885d3b5d55e821316b7e3325a5fb14b30807747aff26a5ba376470766d91

[mrpollo]

The biggest issue with the cross-compiler container for development is the image size of >5gb, which non-surprisingly comes from installing /Tools/setup/ubuntu.sh

If we dive into the image to inspect its contentsd this is what we find:

1. the setup layer is 5gb
2. most of it is in /usr/lib/arm-none-eabi/ (2.5gb)
3. the other remaining fatty culprits are:

• 597mb /usr/lib/aarch64-linux-gnu
• 480mb /usr/lib/gcc/arm-none-eabi

[julianoes]

Just a few nitpicks.

[sfuhrer]

@mrpollo now that release 1.16 is branched off, can we get this in? Or what's our approach to update the compiler?
Many of us are desperately waiting for the flash efficiency gains that come along with it.

[mrpollo]

Let's discuss on the Dev Call @sfuhrer

[DronecodeBot]

This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there:

https://discuss.px4.io/t/px4-team-sync-and-community-q-a-may-6-2025/45433/2

[DronecodeBot]

This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there:

https://discuss.px4.io/t/px4-dev-call-may-14-2025-team-sync-and-community-q-a/45516/1