Skip to content

Running "unserialize"

Executing the dockerized "unserialize"

Note

2025-08-29: As of mbari/tethysdash:4.98.0, the unserialize executable is no longer included in the image. See the TethysDash ChangeLog.

  • Primarily for TehysDash purposes, we still continue creating and using a separate image with the unserialize tool. The latest version is mbari/lrauv-unserialize:2025-08-06_3e445dd20 at time of this writing. More details about how it is created can be found here.
  • The description below is kept mainly for reference, but can be adapted to the new image, where /opt/lrauv-application/bin/unserialize is the location of the executable inside the container.

TL;DR

Just execute the following on the host where the TethysDash system is running:

docker exec -it tethysdash /opt/tethysdash/tools/unserialize [arguments...]

NOTE: Any path-related arguments above (including the location of the unserialize executable itself) will refer to the filesystem in the tethysdash container, not the host.

More in detail

  • The "unserialize" executable will of course not only run inside the container but access and generate any files also within the container.

  • The executable is located at /opt/tethysdash/tools/unserialize in the container, so you can trigger its execution from the host as follows:

    docker exec -it tethysdash /opt/tethysdash/tools/unserialize [arguments...]
    NOTE: With any path-related arguments referring to the filesystem within the tethysdash container.

  • As explained in the docker based installation page, the $TETHYSDASH_DATA environment variable indicates the host directory under which TethysDash generates a number of subdirectories and files:

    • /<vehicleName>/realtime/*
    • /<vehicleName>/realtime/argologs/*
    • /<vehicleName>/realtime/sbdlogs/*
    • /<vehicleName>/missionlogs/<year>/*.dlist

  • $TETHYSDASH_DATA is mapped to /opt/tethysdash/data inside the tethysdash container.

  • So, you can run "unserialize" on the host keeping in mind that any relevant path arguments will correspond to the filesystem in the container itself. In particular, you will want to indicate such arguments in a way that the corresponding files are available on the host in corresponding locations under $TETHYSDASH_DATA.