Noble Containers

[alexcekay]

Solved Problem

As discussed in the dev call, we want to use a newer GCC version for compiling PX4 in the future, as newer versions take way less FLASH.

Solution

This PR creates new containers that are based oon Ubuntu Noble. As discussed we will use the GCC version shipped with Ubuntu Noble to compile on the CI. This is GCC13. I however needed to use the GCC13 version from ARM, as the one shipped via Noble did not compile due to: cannot read spec file 'nosys.specs': No such file or directory

I added myself as a maintainer, just to have something entered into the new files. Of course, if the container maintenance is defined differently, we can just change it.

Testing

I switched the CI jobs to use the containers of this PR in my fork: alexcekay/PX4-Autopilot#19

[dagar]

Adding this to PX4-containers now seems fine, but if the goal is to shortly bump things within PX4-Autopilot we should just do that directly with the in tree Dockerfile + setup script.

If that's what you're talking about let's sync up tomorrow and just get it done?

[alexcekay]

Hi @dagar,

My target is to get the CI to build PX4 with GCC13. So I updated the containers to noble which uses GCC13.
As a next step I will create a PR on PX4-Autopilot that bumps the used docker containers to those new noble containers.
Basically the changes that can be seen here: https://github.com/alexcekay/PX4-Autopilot/pull/19/files
What exactly do you want to do instead?

Btw: Are you or @mrpollo admin of the PX4 docker hub account? There seems to be a problem pushing the containers to it:
https://github.com/PX4/PX4-containers/actions/runs/13281776545/job/37081533861. It looks like a credentials topic and I can't change the settings of this repo. Thanks guys.