Update VISSR version (latest VISS v3)

[slawr]

CDSP currently uses an VISSR commit that points at in-development support for VISS v3. The upstream project has now completed development of VISS v3 support and we should upgrade

Work plan:

• Determine upstream commit to use
• Check upstream Dockerfile builds (upstream does not maintain their Dockerfile alongside code updates)
• Sanity test that IoTDB connector still works for get/set
• Check if any CDSP documentation needs updating

[slawr]

Upstream commit

Upstream recently made release v1.0. However on inspection the tag is 200 commits behind master. Asked maintainers whether that is expected.

[slawr]

Placing on hold whilst waiting for feedback from upstream maintainers

[slawr]

Upstream #commit

Ulf reported that tag was pointing at wrong commit and corrected it.
Resumed development on that current head commit 9f59c4f720.

VISSR build

Experienced build issue using the upstream Dockerfile.rlserver. Raised issue in upstream VISSR COVESA/vissr#115
Waiting for feedback from VISSR devs.

[slawr]

After discussion with VISSR maintainers sent fix for COVESA/vissr#115 which has been merged.

VISSR now builds.

VISSR startup

A new problem was discovered sanity testing startup of the VISSR image. See COVESA/vissr#118
Placing ticket on hold whilst wait for maintainer feedback

[slawr]

Maintainer fixed VISSR # 118. Updated to the new commit. It fixed the reported errors.

However new runtime errors were discovered related to Unix domain sockets. Since the last VISSR update support has been added for unix domain sockets that are placed in the directory /var/tmp/vissv2/. These were seemingly not being created in the docker deployment as the VISSR service was starting, but failing to run. The docker log for vissv2server contained errors such as:
vissv2server | {"file":"serviceMgr.go:1019","level":"info","msg":"initFeederRegServer:UDS listen failed, err = listen unix /var/tmp/vissv2/feederReg.sock: bind: no such file or directory","time":"2026-02-19T17:03:37Z"}

The solution was to add this directory to the list of docker volumes created by the tmp service and used by the VISSR components

cdsp/docker/docker-compose-cdsp.yml

Line 101 in c78dca2

volumes:

No further errors were found and VISSR would now succesfully run

Sanity testing

Successfully started CDSP and used the VISSR web client to connect to VISSR and perform get/set operations in the Apache IoTDB DB.

Documentation

No adjustments were found to be needed in the CDSP documentation.

PR

Created PR #87
Asked @chrizmc to review