Development environment troubleshoots

[alexandrebrg]

This post groups all issues we encounter during development of RIK, it is a pending issue, and once we got enough entries, we will create a PR to improve the developer setup guide and the troubleshoot page.

If you encounter any problem with setup RIK and you have a solution for it (or not), feel free to respond to this issue.

---

I need to run riklet as root but I can't because cargo isn't available in root

Cargo allows for a config file, the file .cargo/config should be added in your local rik repository. You can configure it to run sudo as a wrapper of all your cargo commands (be aware it will also run controller / scheduler as root).

# .cargo/config
[target.x86_64-unknown-linux-gnu]
runner = 'sudo -E'

---

I want to have more logs in my RIK cluster

Each component is configured the same way, with tracing. You can configure its verbosity level with the environment variable RUST_LOG. Examples:

# Put log level trace for all components and its rust dependencies
RUST_LOG=trace

# Put log level trace for riklet
RUST_LOG=riklet=trace

# Put log level debug for riklet and trace for firepilot
RUST_LOG=riklet=debug,firepilot=trace