The default protocol that Cargo is using to download its index of crates is somehow too resource-consuming when the ODK is built under BuildKit (to build multiarch image). So we force Cargo to use the new HTTP-based "sparse" protocol, which is supposedly much more efficient and does not seem to cause issue with BuildKit.
This is the same as #933, but applied to the 1.4 branch.
The default protocol that Cargo is using to download its index of crates is somehow too resource-consuming when the ODK is built under BuildKit (to build multiarch image). So we force Cargo to use the new HTTP-based "sparse" protocol, which is supposedly much more efficient and does not seem to cause issue with BuildKit.
This is the same as #933, but applied to the 1.4 branch.