If one has podman-docker installed (a wrapper for podman that emulates docker's CLI, needed for things like docker-compose to be compatible), cross fails:

cross build --release --target=aarch64-unknown-linux-gnu

Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
error: failed to open: /target/release/.cargo-lock

Caused by:
  Permission denied (os error 13)

It looks like cross is trying to use docker, but since my user doesn't have access to "docker" (the emulated interface) it fails.

Without podman-docker, everything works perfectly fine using rootless podman containers.

Cross should probably either default to trying podman first and then falling back to docker, or have some sort of check so this doesn't happen.