Cluebase VMS Installation Manual

From vCloud.ai Documentation
Revision as of 09:27, 18 May 2026 by Vcloudai (talk | contribs)
Jump to navigation Jump to search

Use this option when Docker is used by other applications on the server.

Everything

This option removes Cluebase VMS and BI and also purges Docker from the server.

It removes:

  • Docker Engine
  • Docker CLI
  • Docker Compose plugin
  • Docker data under /var/lib/docker
  • Docker configuration under /etc/docker
  • Docker socket and related files

⚠️ Warning: This option destroys all Docker containers, images, and volumes on the host, including containers unrelated to Cluebase VMS. The installer requires typed confirmation before continuing.

Advanced Options

Force architecture

Use ARCH_OVERRIDE to force architecture detection:

<syntaxhighlight lang="bash"> ARCH_OVERRIDE=arm64 ./install.sh --dry-run </syntaxhighlight>

This is mainly useful for testing.

Disable colored output

Use:

<syntaxhighlight lang="bash"> NO_COLOR=1 ./install.sh </syntaxhighlight>

This disables ANSI color output in the installer menus.

Offline Installation Note

The bundled README references these offline commands:

<syntaxhighlight lang="bash"> sudo ./offline_installer.sh sudo ./offline_update.sh </syntaxhighlight>

The attached installer archive inspected for this manual does not contain offline_installer.sh or offline_update.sh. Offline installation therefore requires a separate offline bundle that includes those scripts, Docker packages, Docker Compose binary, and pre-pulled image tarballs.

Troubleshooting

Docker group permissions

After Docker installation, the installer adds the current user to the docker group. The current terminal session may not receive the new group permission immediately.

If Docker commands require sudo after installation, log out and log back in, then try again.

Docker daemon is not ready

If Docker does not become ready, check:

<syntaxhighlight lang="bash"> sudo systemctl status docker sudo journalctl -u docker -n 50 </syntaxhighlight>

GPU mode fails

If GPU mode fails, check:

<syntaxhighlight lang="bash"> nvidia-smi docker info | grep -i nvidia </syntaxhighlight>

If nvidia-smi does not work, install or repair the NVIDIA driver first, then rerun the installer.

Port already in use

If the web interface does not open, check whether required ports are already used:

<syntaxhighlight lang="bash"> sudo ss -tulpn </syntaxhighlight>

Free the required port or change the deployment configuration before starting the services again.

Database does not become ready

Check the database logs:

<syntaxhighlight lang="bash"> docker logs vms-db --tail 200 </syntaxhighlight>

The installer waits for the message indicating that MySQL is ready for connections.

Migrations do not complete

Check migration logs:

<syntaxhighlight lang="bash"> docker logs vms-migration --tail 200 </syntaxhighlight>

The installer waits for migration success before starting the remaining Cluebase services.

Check running containers

Use:

<syntaxhighlight lang="bash"> docker ps </syntaxhighlight>

or, if Docker requires sudo:

<syntaxhighlight lang="bash"> sudo docker ps </syntaxhighlight>

Expected Cluebase containers may include:

  • vms-server
  • vms-live-server
  • vms-web
  • vms-db
  • vms-nginx
  • vms-rtsp-server
  • vms-va
  • vms-ai, if AI was selected
  • vms-lpr, if LPR was selected

Expected BI containers may include:

  • bi-postgres
  • bi-redis
  • bi-migration
  • bi-api
  • bi-runner
  • bi-streamer
  • bi-dispatcher
  • bi-ui
  • bi-nginx