cross build / run cannot find container images

[JosiahParry]

I am trying to use cross to cross-compile on my mac M1 and it unfortunately doesn't "just work."

After installing the required toolchains all commands result in the following docker error:

$ cross build --target aarch64-unknown-linux-gnu
Unable to find image 'ghcr.io/cross-rs/aarch64-unknown-linux-gnu:0.2.5' locally
0.2.5: Pulling from cross-rs/aarch64-unknown-linux-gnu
docker: no matching manifest for linux/arm64/v8 in the manifest list entries.
See 'docker run --help'.

Is there a bug in the version that is available from cargo binstall? Does a registry need to be configured?

[Emilgardis]

Please see #1214

either you can use cross from the main branch, or once (per target) run cross with CROSS_CONTAINER_OPTS="--platform linux/amd64" CROSS_BUILD_OPTS="--platform linux/amd64" cross ...

[xaocon]

It looks like this has been around for a while and aarch64 is getting more and more common. It might be helpful to make these instructions a little easier to find. Would you like for me to make a PR for the README and maybe update the wiki to guide people a bit more? Either highlighting the need to install from from git if you're working from an aarch64 host or the workaround in both places and adding the rustup toolchain install stable-x86_64-unknown-linux-gnu --force-non-host info to the README? I think the git instructions are probably the way to go, depending on how reliable main is (looks like things are generally well cared for).