Pricing
00
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 Pro

Operator 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

01

System boundary

Trace only the relevant path.

3 nodes
  1. 01host can0→
  2. 02container network namespace→
  3. 03SocketCAN applicationOUT
02

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.

03

Verification

Pass more than the visible symptom.

4 checks
  • Container sees can0
  • Container remains non-privileged
  • Hidden regression behavior
  • Root cause explanation