Unified Docker image and external ROS 2 Jazzy workspace for:

• jackal_nav2, which provides sensors, localization, and navigation.
• jackal-serial, which provides low-level serial control, ros2_control, robot description, and RC/ joystick teleoperation.

The image defaults to kumarrobotics/jackal_autonomy:latest and extends the existing local kumarrobotics/dcist-master-jazzy-nvda:latest image as-is. This base image is not rebuilt. If it is not available locally, refer to the dcist_master_jazzy repository.

Application source is not copied into the derived image. The host-populated ws directory is bind-mounted at /home/dcist/dcist_ws, so autonomy and low-level control share one workspace and one container runtime. The inherited base may contain a legacy workspace in older layers; the runtime bind mount hides it.

The pinned submodules under ws/src provide the complete source closure for the unified runtime:

The jackal_serial submodule stays as one repository at ws/src/jackal_serial. Colcon recursively discovers its individual ROS packages; they do not need to be copied or built one by one.

sync_workspace.bash performs Git submodule operations on the host and uses a robot validated SSH key by default; the key must have mode 600. Set JACKAL_AUTONOMY_SSH_KEY to override the key path. The selected key must have read access to the repositories listed in .gitmodules.

git clone <this-repository-url> jackal_autonomy
cd jackal_autonomy
./sync_workspace.bash
./build.bash
./run.bash

Both build and run default to kumarrobotics/jackal_autonomy:latest. Builds are allowed to overwrite that tag. Use the same tag option to build, run, or join a named variant:

./build.bash --tag experiment
./run.bash --tag experiment
./join.bash --tag experiment

Inside the container, one workspace command installs declared dependencies and runs one colcon build for both autonomy and low-level control:

jackal-build
source /home/dcist/dcist_ws/install/setup.bash
jackal-test

Run ./sync_workspace.bash manually after cloning and whenever you intentionally want to restore the submodules to the commits pinned by the outer repository. Take caution to always commit any submodule changes in this repository before running the sync script, because it will reset the submodules to the recorded commits.

To advance each submodule to the head of the branch recorded in .gitmodules, use the explicit update mode and then review and commit the changed gitlinks:

./sync_workspace.bash --remote

The launcher preserves the prior robot-container experience: UID 1000, GPU and X11 access, host networking, privileged device access, persistent data and .ros_docker mounts, the external workspace, dialout/input/video groups, and a host-editable bashrc.

The image and container shell default to Fast DDS:

echo "$RMW_IMPLEMENTATION"
# rmw_fastrtps_cpp

The serial bringup does not start a Zenoh router. Keep all autonomy and serial processes on the same ROS_DOMAIN_ID and RMW_IMPLEMENTATION.

The base image's /etc/clearpath remains active by default. To replace it with a robot-specific host configuration, set an explicit directory:

CLEARPATH_DIR=/path/to/clearpath ./run.bash

The tracked data/configs/zed2i.yaml is mounted over the ZED wrapper's default configuration to retain the existing HD2K, 15 Hz, 15 m robot tuning while keeping the ZED submodule clean. It disables ZED depth stabilization and visual positional tracking because DLIO is the robot odometry source; this prevents the unused tracking module from blocking camera and IMU publication.

The tracked data/configs/usr/local/zed/settings/SN34141806.conf is also mounted read-only at /usr/local/zed/settings for offline camera calibration. Set JACKAL_AUTONOMY_ZED_SETTINGS to use a different settings directory.

Serial, sensors, and navigation deliberately remain separate processes so each part can be started and stopped independently:

• Launch the low-level serial, ros2_control, robot-state-publisher, and teleoperation stack:

  ros2 launch jackal_launch jackal_serial.launch.py

  Inside the container, the equivalent convenience alias is jackal-serial.

• Launch the Ouster lidar, ZED camera, and DLIO localization stack:

  ros2 launch jackal_nav2 jackal_sensors.launch.py

  Inside the container, the equivalent convenience alias is jackal-sensors.

• Launch GroundGrid obstacle processing, Nav2, static transforms, and the navigation command bridge:

  ros2 launch jackal_nav2 jackal_navigation.launch.py

  Inside the container, the equivalent convenience alias is jackal-navigation.

• Record a selected profile of autonomy and sensor topics to a rosbag:

  ros2 launch jackal_nav2 record_jackal.launch.py

  Inside the container, the equivalent convenience alias is jackal-record. The default recording profile is navigation; the other available profiles are lidar, semantic, and full.

• Send a sequence of waypoint goals from a YAML file to Nav2:

  ros2 run jackal_nav2 goto_nav2 /path/to/waypoints.yaml

  Inside the container, the equivalent convenience alias is:

  jackal-goto /path/to/waypoints.yaml

For example, the three main runtime stacks can be launched independently with:

jackal-serial
jackal-sensors
jackal-navigation