Skip to main content
Running the agent as a container? See Docker Deployment for how to upgrade it.
To upgrade the Odigos VM Agent, run the following based on your Linux package manager:
Using dnf (RHEL, Fedora, Rocky Linux):

What an upgrade changes

Starting from version v0.1.106, every upgrade switches the agent to non-root, including a host that has been running as root. During the upgrade, the package:
  • Moves leftover /etc/odigos-vmagent/* into /var/lib/odigos-agent/config/, then deletes /etc/odigos-vmagent
  • Moves agent logs from /var/log into /var/lib/odigos-agent/log/
  • Chowns /var/odigos and /etc/odigos-otelcol to the odigos user
  • Adds odigos to the docker group when that group exists
  • Disables odigos-otelcol.service (the collector becomes a child of the agent)
  • Re-renders /etc/systemd/system/odigos-vmagent.service.d/nonroot.conf unless you replaced its # Managed by the odigos-vmagent package header
Config and logs still move to /var/lib/odigos-agent even if you stay on root. Only the service user stays root.
To stay on root, set the mode before the upgrade:
Hosts that cannot grant ambient capabilities (systemd older than 229) stay on root automatically.
After a root-to-non-root migration, review Additional permissions.

Migrate an existing root install

To switch a running root host to non-root without waiting for the next package upgrade:
--dry-run prints the plan only. The migrate tool performs the same steps as an upgrade.