In productionProbeginnerContainer capability
The container cannot open CAN
Expose one CAN interface without running the entire container privileged.
Pairs with Containers, devices, and networking in Production ROS Operations. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
`can0` exists on the host but is absent in the application network namespace.
Ubuntu 24.04, ROS 2 Jazzy, Cyclone DDS, containers, systemd, OpenTelemetry fleet sandbox
System boundary
Trace only the relevant path.
host can0container network namespaceSocketCAN application
How this lab works
You diagnose it — no command list.
Open the repair workspace and gather your own evidence in a real terminal. No diagnostic commands are handed to you — finding the fault is the exercise. Stuck? Progressive hints unlock inside the workspace.
Verification
Your repair must pass more than the visible symptom.
- Container sees can0
- Container remains non-privileged
- Hidden regression behavior
- Root cause explanation