Skip to content
Closed
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/USAGE.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,8 @@ Remoteproc Runtime supports several container engines, but the specifics of inte
- **[Container Runtime (Podman)](#container-runtime-podman)** - For Podman deployments
- **[Container Runtime (standalone)](#container-runtime-standalone)** - For direct OCI runtime usage

Accessing and controlling remoteproc devices typically requires root permissions, as the driver interfaces are located in the /sys/class directory. To ensure Remoteproc Runtime has the necessary privileges, run your container engine (e.g., Docker daemon, K3S, or Podman) with root privileges (typically via `sudo`), so that it can spawn containers with Remoteproc Runtime running as root.
Comment thread
yejseo01 marked this conversation as resolved.
Outdated

### Containerd Shim (Docker, K3s, etc)

1. **Install the shim and runtime**
Expand Down