sh: 1: cargo: Permission denied

[Barugon]

I'm getting this error now. Anyone know what this is and how to get past it?

[Emilgardis]

need a little more information, see the big issue #260 which has been split up and most issues solved (only known remaining issue is on wsl)

the error message is telling that, somehow, cargo is not in path.

if you run cross with -v added you'll see what cross tries to do and how it invokes cargo in the container, the issue might be that your rustup installation for the x86_64-unknown-linux-gnu toolchain is wrong, it could be docker failing to mount the sysroot, etc etc.

[Barugon]

Here's the output:

[barugon@shaguar cota]$ cross build -v --release --target=x86_64-unknown-linux-gnu
+ cargo metadata --format-version 1 --filter-platform x86_64-unknown-linux-gnu
+ rustc --print sysroot
+ rustup toolchain list
+ rustup target list --toolchain stable-x86_64-unknown-linux-gnu
+ rustup component list --toolchain stable-x86_64-unknown-linux-gnu
+ /usr/bin/podman
+ /usr/bin/podman run --userns host -e 'PKG_CONFIG_ALLOW_CROSS=1' -e 'XARGO_HOME=/xargo' -e 'CARGO_HOME=/cargo' -e 'CARGO_TARGET_DIR=/target' -e 'CROSS_RUNNER=' -e TERM -e CARGO_REGISTRIES_CRATES_IO_PROTOCOL -e 'USER=barugon' --rm -v /home/barugon/.xargo:/xargo:z -v /home/barugon/.cargo:/cargo:z -v /cargo/bin -v /home/barugon/Desktop/Dev/cota:/project:z -v /home/barugon/.rustup/toolchains/stable-x86_64-unknown-linux-gnu:/rust:z,ro -v /home/barugon/Desktop/Dev/cota/target:/target:z -w /project -i -t ghcr.io/cross-rs/x86_64-unknown-linux-gnu:0.2.5 sh -c 'PATH=$PATH:/rust/bin cargo build -v --release --target=x86_64-unknown-linux-gnu'
sh: 1: cargo: Permission denied
+ rustup component list --toolchain stable-x86_64-unknown-linux-gnu

I have no problem running cargo build --release --target=x86_64-unknown-linux-gnu. Also, this issue started recently (within the last two months).

[Emilgardis]

aha! I misread the title, my bad :)

The error actually suggests that podman + the user can't read the binary, not what's in #260

So, can you check

ls -la /home/barugon/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin

it should return something like -rwxr-xr-x 1 barugon root 26058856 Jan 27 00:56 cargo on cargo and the other binaries

if everything looks ok, try

podman run --userns host -e 'USER=barugon' --platform=linux/amd64 --rm -v /home/barugon/.rustup/toolchains/stable-x86_64-unknown-linux-gnu:/rust:z,ro -it ubuntu:20.04 /rust/bin/cargo -V

[Barugon]

Listing the files, I get:

total 67832
drwxr-xr-x. 1 barugon barugon      172 Mar  9 11:08 .
drwxr-xr-x. 1 barugon barugon       42 Mar  9 11:08 ..
-rwxr-xr-x. 1 barugon barugon 26574240 Mar  9 11:08 cargo
-rwxr-xr-x. 1 barugon barugon  1367128 Mar  9 11:08 cargo-clippy
-rwxr-xr-x. 1 barugon barugon  5676264 Mar  9 11:08 cargo-fmt
-rwxr-xr-x. 1 barugon barugon 12290400 Mar  9 11:08 clippy-driver
-rwxr-xr-x. 1 barugon barugon  2759496 Mar  9 11:08 rustc
-rwxr-xr-x. 1 barugon barugon 14600032 Mar  9 11:08 rustdoc
-rwxr-xr-x. 1 barugon barugon  6168720 Mar  9 11:08 rustfmt
-rwxr-xr-x. 1 barugon barugon      759 Mar  9 11:08 rust-gdb
-rwxr-xr-x. 1 barugon barugon     1933 Mar  9 11:08 rust-gdbgui
-rwxr-xr-x. 1 barugon barugon     1072 Mar  9 11:08 rust-lldb

[Emilgardis]

had another user with this problem on podman + SELinux, the solution to fix it was to reinstall rustup + rust. Are you able to try that?

[Barugon]

It turns out that I currently don't need it as I'm able to build on Fedora 37 and run on Ubuntu 22.04 LTS.