demo-rust-axum VS rust-musl-cross

I like Axum, Hyper, Tower, Tokio, Serde. I wrote a quick start guide here: https://github.com/joelparkerhenderson/demo-rust-axum (and any constructive advice is welcome)

Demo Rust Axum has source and a free e-book PDF: https://github.com/joelparkerhenderson/demo-rust-axum

source of code snippet

Axum is an excellent web framework. I've used Actix, Rocket, Warp, Tide too. If you want a quick Axum demo, I wrote a free 50-page ebook tutorial here: https://github.com/joelparkerhenderson/demo-rust-axum

Is my best bet just to use (rust-musl-cross)[https://github.com/messense/rust-musl-cross] as the builder image?

rust-musl-cross: active as last commit was 10 days ago. It said it based on rust-musl-builder. But this repo was created years ago. So why would this exist when there is also rust-musl-builder. What are the differences compared to rust-musl-builder and muslrust?

The example that is provided in the AWS Rust runtime repository shows them using a custom linker and rustup target in order to cross-compile for x86-based lambdas. I attempted to dive into how to get a arm64-based linker, but in the process of trying to figure out how to get that linker installed locally (no convenient packages for Ubuntu, sorry), I stumbled across a project that provides cross-compilation tooling for various platforms via Docker. That made my life a lot easier - Using the rust-musl-cross Docker container, all I have to do is wrap the call to cargo build, and it builds for the proper architecture: