Rust "target may not be installed" - rustup target add in CI

By Kaveh Alemi·Latchkey

A --target build references a target triple that rustup hasn’t installed. The host toolchain is fine, but the cross-compilation target’s components were never added, so cargo can’t build for it.

What this error means

cargo build --target ... fails noting the target "may not be installed" or that the target is unknown. Frequently seen for wasm32-unknown-unknown, musl, or ARM targets on a fresh runner.

error[E0463]: can't find crate for `core`
note: the `wasm32-unknown-unknown` target may not be installed
help: consider downloading the target with `rustup target add wasm32-unknown-unknown`

Common causes

Cross target never added

Targets like wasm32-unknown-unknown or x86_64-unknown-linux-musl aren’t installed by default. Building for them without rustup target add fails to find core/std.

Fresh runner without cached targets

A cold runner starts with only the host target. Any cross build needs the target component re-added each run unless the toolchain is cached.

How to fix it

Add the target before building

rustup target add wasm32-unknown-unknown
cargo build --target wasm32-unknown-unknown

List installed targets to verify

Confirm which targets rustup actually has before the build step.

rustup target list --installed

How to prevent it

• Add cross targets in the setup action’s targets: list.
• Cache ~/.rustup so installed targets persist across runs.
• Assert the target is installed before the build step.

Frequently asked questions

Related guides

References

• The Cargo Book
• GitHub Actions documentation