Not sure why "MUSL-compatible" is the default for the binary install. This is surely in the minority of Linux distros, even in 2024. I imagine it's best (when distributing) to target the convenience of the end-user rather than of the dev team (since one could simply create a separate CICD channel that builds with a glibc-based starting image).

Makes me wonder if the 'cargo install' method requires MUSL libc. This is not stated but that also makes it unclear since it comes right after the former variant.