Emilgardis

@CoreyCole this is the wrong issue for your problem, please create a new issue as a quick mention, the table in the readme is only for the current `:main` images,...

with the username fixed, I suspect your username is not `foo`

is docker working at all? ``` $ docker run hello-world ```

do `docker images "ghcr.io/cross-rs/x86_64-pc-windows-gnu"` and post the output first before pulling

the `[target.aarch64-unknown-linux-gnu]` is part of the Cross config, see https://github.com/cross-rs/cross#configuration so, to fix change to ```toml [package.metadata.cross.target.aarch64-unknown-linux-gnu] image = "ghcr.io/cross-rs/x86_64-pc-windows-gnu:0.2.4" [package.metadata.cross.target.x86_64-pc-windows-gnu] image = "ghcr.io/cross-rs/x86_64-pc-windows-gnu:0.2.4" ```

We shouldn't currently use that at all, instead you'd have to place the config in `.cargo/config.toml`in the manifest root if you want it to go over to the `cross` builder...

Note that that feature is currently unreleased, you'd have to install from git `cargo install cross --git https://github.com/rust-embedded/cross`

I'll try to get in a fix for this. Not sure exactly what is happening but have an idea how to solve it.

I'd forgotten about this, this can be solved by us setting `CARGO_TARGET__LINKER` in every image we provide, since env vars take priority over toml values. However, this still feels like...

> I tried `export CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_LINKER="aarch64-linux-gnu-gcc" ; cross build --target aarch64-unknown-linux-gnu`, It only works if my `config.toml` is not present. This is correct, however you need to forward it to the...