I spoke with someone recently who had some trouble figuring out how to run Cargo-built binaries directly, until they realized that cargo run sets LD_LIBRARY_PATH, which is not documented. When running cargo run -v, cargo shows the binaries it runs, but not the setting of LD_LIBRARY_PATH. Please include that in the emitted command line invocations (e.g. LD_LIBRARY_PATH=... target/release/...) when using -v, to make it more obvious what cargo run does.