[Bug]: Rust & Cargo missing for Rocky9 docker build

Find the Rocky9-CY2024 Dockerfile and inspect its dnf install list, then reproduce the rvbootstrap Docker build to confirm the missing Rust compiler failure. Done means the Rocky9-CY2024 build completes with the required Rust and Cargo dependencies, with the impact on other platforms checked.

What happened?

Following the steps for a docker build with Rocky9-CY2024, the rvbootstrap command fails, due to missing rust & cargo.

It seems to be required for the cryptography python module build.

The fix is adding:

rust \
cargo \

... to the dockerfile's dnf installs.
I am not sure if this is required for other platforms as well.

List all the operating systems versions where this is happening

Rocky9-CY2024 docker (Fedora 42 host)

On what computer hardware is this happening?

x86_64, rest irrelevant

Relevant console log output

...
      copying src/cryptography/hazmat/bindings/_rust/openssl/x448.pyi -> build/lib.linux-x86_64-cpython
-311/cryptography/hazmat/bindings/_rust/openssl
      running build_ext
      running build_rust
      error: can't find Rust compiler

      If you are using an outdated pip version, it is possible a prebuilt wheel is available for this p
ackage but pip is not able to install from it. Installing from the wheel would avoid the need for a Rus
t compiler.

      To update pip, run:

          pip install --upgrade pip

      and then retry package installation.

      If you did intend to build this package from source, try installing a Rust compiler from your sys
tem package manager and ensure it is on the PATH during installation. Alternatively, rustup (available
at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.

      This package requires Rust >=1.63.0.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for cryptography
  ...

Environment variables

No response

Extra information

No response

Code of Conduct

• I agree to follow this project's Code of Conduct