📖
Cerulean Sonar Docs
Docs DirectoryStore
SonarView
SonarView
  • Overview
  • Installation
    • Linux
    • macOS
    • Windows
    • BlueOS
    • Docker
  • App Bar Controls
  • Device Discovery and IP Addressing
  • Application Settings
  • Replaying Saved Sonar Files
  • Session Configurations
    • Multiple Omniscans
    • Surveyor + NMEA Heading/Position
    • Omniscan + MAVLink2Rest Position
    • Omniscan + NMEA Heading/Position
  • UTC Time
  • Device Specific Controls
    • Omniscan 450
      • Mounting Setup
      • Device Controls
      • Firmware Update
      • Display Controls
      • Replay Controls
    • S500 Sounder
    • Ping
    • Ping360
  • Hotkeys
  • SonarLink
  • Known Issues
  • Troubleshooting
  • Deprecated
    • Mission Configurations
      • Omniscan 450
      • Surveyor 240-16
  • Legal
Powered by GitBook
On this page
  1. Installation

Docker

PreviousBlueOSNextApp Bar Controls

Last updated 5 months ago

Configuration:

  • You'll need to specify the directory that SonarView should save to in your host OS, which is mapped to /userdata in the container. This is where log files will be saved, and this is where your SonarView config will live./usr/SonarView is used for this example.

  • The container needs to run in the host network (--net=host) in order to be able to scan the network for available sonars. Device discovery can not work without host network mode.

  • --restart=unless-stopped will automatically start the container on each boot.

Get started:

sudo docker run -d -v /usr/SonarView:/userdata --net=host --name=sonarview --restart=unless-stopped nicknothom/sonarview:1.11.6

After the container starts, the SonarView Web UI should be available on port 7077 of your host.

Note: The container will need to be updated manually.

BlueOS users should probably use the BlueOS Extension Store instead. These instructions describe how to run SonarView in a generic docker environment.

Docker Builds of SonarView here.