Request: docs about installing using cargo

[erlangparasu]

via cargo install netavark

https://crates.io/crates/netavark

[Luap99]

What exactly is the question?

The binary must be placed in a specific directory for podman to discover it (see helper_binaries_dir in containers.conf) and I think by default cargo install would place the binary in a user local $PATH which woul dnot make it work by default.
And we do have a test only binary (netavark-dhcp-proxy-client) that should not be installed on normal systems but the install command would pick it up from Cargo.toml by default.
Also we ship several systemd units as well that cannot be handled by cargo install either.

So overall I would recommend against using cargo install. That said I do agree that we do not have any specific install instructions in this repo.

[erlangparasu]

What exactly is the question?

The binary must be placed in a specific directory for podman to discover it (see helper_binaries_dir in containers.conf) and I think by default cargo install would place the binary in a user local $PATH which woul dnot make it work by default. And we do have a test only binary (netavark-dhcp-proxy-client) that should not be installed on normal systems but the install command would pick it up from Cargo.toml by default. Also we ship several systemd units as well that cannot be handled by cargo install either.

So overall I would recommend against using cargo install. That said I do agree that we do not have any specific install instructions in this repo.

oh i see. i just think its easier to use cargo to build the netavark binary, its ready to use. Also i have tried using cargo install, and create symlink to specific podman's needs: /usr/local/libexec/podman/netavark. it works well for now