NxWitness

Docker images for Network Optix Nx Witness and OEM-branded VMS products.

This is a project to build and publish Docker images for various Network Optix VMS products, in an Ubuntu and a LinuxServer base image variant of each product.

Build and Distribution

Source Code: GitHub for source, issues, and CI/CD pipelines.
Versioned Releases: GitHub Releases for version-tagged source archives.
Docker Images: Docker Hub for the published container images.

Build Status

Releases

Docker releases:

NxWitness:

NxWitness-LSIO:

NxMeta:

NxMeta-LSIO:

NxGo:

NxGo-LSIO:

DWSpectrum:

DWSpectrum-LSIO:

WisenetWAVE:

WisenetWAVE-LSIO:

Release Notes

Version: 2.15:

Summary:

Build, CI, and repository tooling changes only. No functional change to the published images.

See Release History for complete release notes and older versions.

Getting Started

Getting started with a simple test compose file:

# compose.yaml

# Test using non persistent docker volumes
volumes:
  test_nxwitness-lsio_config:
  test_nxwitness-lsio_media:
  test_nxwitness-lsio_backup:
  test_nxwitness-lsio_analytics:

services:
  nxwitness-lsio:
    # Use the image matching your product
    image: docker.io/ptr727/nxwitness-lsio:stable
    container_name: nxwitness-lsio-test-container
    restart: unless-stopped
    network_mode: bridge
    ports:
      # Expose the service on port 7203
      - 7203:7001
    environment:
      - TZ=America/Los_Angeles
    volumes:
      # Map to your real storage in production
      - test_nxwitness-lsio_config:/config
      - test_nxwitness-lsio_media:/media
      - test_nxwitness-lsio_backup:/backup
      - test_nxwitness-lsio_analytics:/analytics
    tmpfs:
      # Keep mediaserver's Unix socket and tmp files in RAM
      - /tmp:size=1g,mode=1777

# Launch the service
docker compose up --detach

# Open your web browser on the local machine port 7203
echo "Nx Witness LSIO:" "https://$HOSTNAME:7203/"

# Shut the service down
docker compose down

Example of a service in production:

networks:

  public_network: # External macvlan network
    name: ${PUBLIC_NETWORK_NAME}
    external: true
  local_network: # External bridge network
    name: ${LOCAL_NETWORK_NAME}
    external: true
  stack_network: # Stack network


services:

  nxmeta:
    image: docker.io/ptr727/nxmeta-lsio:latest
    container_name: nxmeta
    hostname: nxmeta
    domainname: ${DOMAIN_NAME}
    restart: unless-stopped
    user: root
    group_add:
      - ${DOCKER_GROUP_ID}
    security_opt: # Set with care
      - seccomp=unconfined
      - apparmor=unconfined
    devices: # Pass through Intel/AMD iGPU for hardware accelerated video
      - /dev/dri
    environment:
      - TZ=${TZ}
      - PUID=${USER_NONROOT_ID} # Run as non-root user
      - PGID=${USERS_GROUP_ID}
    volumes: # ZFS volumes
      - ${APPDATA_DIR}/nxmeta/config:/config
      - ${NVR_DIR}/media:/media # ssdpool/nvr-media
      - ${NVR_DIR}/backup:/backup # hddpool/nvr-backup
      - ${NVR_DIR}/analytics:/analytics # ssdpool/nvr-analytics
    tmpfs: # Keep mediaserver's Unix socket and tmp files in RAM
      - /tmp:size=1g,mode=1777
    networks:
      public_network:
        ipv4_address: ${NXMETA_IP} # Static IP
        mac_address: ${NXMETA_MAC} # Static MAC
      local_network:
      stack_network:
    labels:
      - traefik.enable=true # Traefik SSL proxy
      # Two-hostname pattern (DNS records configured externally, e.g.
      # in your LAN DNS or hosts file): an A/AAAA `nxmeta -> ${NXMETA_IP}`
      # points at the dedicated macvlan IP above for direct access,
      # and a CNAME `nxmeta-web -> <traefik-host>` fronts the service
      # with SSL termination. Traefik routes only the `-web` hostname;
      # the bare hostname bypasses Traefik entirely.
      - traefik.http.routers.nxmeta.rule=HostRegexp(`^nxmeta-web${DOMAIN_REGEX}$$`)
      - traefik.http.services.nxmeta.loadbalancer.server.scheme=https
      - traefik.http.services.nxmeta.loadbalancer.server.port=7001

Products

The project supports the following product variants:

Network Optix Nx Witness VMS (not available for purchase in the US)
Network Optix Nx Meta VMS (developer and early access version of Nx Witness)
Network Optix Nx Go VMS (version of Nx Witness targeted at transportation sector)
Digital Watchdog DW Spectrum IPVMS (US licensed and OEM-branded version of Nx Witness)
Hanwha Vision Wisenet WAVE VMS (US licensed and OEM-branded version of Nx Witness)

Overview

Introduction

I ran DW Spectrum in my home lab on an Ubuntu Virtual Machine, and was looking for a way to run it in Docker. At the time Network Optix provided no support for Docker, but I did find the The Home Repot NxWitness project, that inspired me to create this project.
I started with individual repositories for Nx Witness, Nx Meta, and DW Spectrum, but that soon became cumbersome with lots of duplication, and I combined all product flavors into this one project.

Today Network Optix supports Docker, and they publish build scripts, but they do not publish container images.

Base Images

The project creates two variants of each product using different base images:

Ubuntu using ubuntu:noble base image.
LinuxServer using lsiobase/ubuntu:noble base image.

The build pipeline also publishes internal base images (ptr727/nx-base:ubuntu-noble and ptr727/nx-base-lsio:ubuntu-noble) built from ubuntu:noble and lsiobase/ubuntu:noble to reduce CI cache churn. These base images are not intended for end-user deployments.

Note that smaller base images like Alpine are not supported by the mediaserver.

LinuxServer

The LinuxServer (LSIO) base images provide valuable container functionality:

The LSIO images are based on s6-overlay, are updated weekly, and LSIO produces containers for many popular open source applications.
LSIO allows us to specify the user account to use when running the mediaserver, while still running the root-tool as root (required for license enforcement).
Running as non-root is a best practice, and required if we need user specific permissions when accessing mapped volumes.
The nxvms-docker project takes a different approach running a compose stack that runs the mediaserver in one instance under the ${COMPANY_NAME} account, and the root-tool in a second instance under the root account, using a shared /tmp volume for socket IPC between the mediaserver and root-tool, but the user account ${COMPANY_NAME} does not readily map to a user on the host system.

Installation

Images are published on Docker Hub:

NxWitness: docker pull docker.io/ptr727/nxwitness
NxWitness-LSIO: docker pull docker.io/ptr727/nxwitness-lsio
NxMeta: docker pull docker.io/ptr727/nxmeta
NxMeta-LSIO: docker pull docker.io/ptr727/nxmeta-lsio
NxGo: docker pull docker.io/ptr727/nxgo
NxGo-LSIO: docker pull docker.io/ptr727/nxgo-lsio
DWSpectrum: docker pull docker.io/ptr727/dwspectrum
DWSpectrum-LSIO: docker pull docker.io/ptr727/dwspectrum-lsio
WisenetWAVE: docker pull docker.io/ptr727/wisenetwave
WisenetWAVE-LSIO: docker pull docker.io/ptr727/wisenetwave-lsio

Images are tagged as follows:

latest: Latest published version, e.g. docker pull docker.io/ptr727/nxmeta:latest.
stable: Latest released version, e.g. docker pull docker.io/ptr727/nxmeta:stable.
rc: Latest RC version, e.g. docker pull docker.io/ptr727/nxmeta:rc.
beta: Latest Beta version, e.g. docker pull docker.io/ptr727/nxmeta:beta
develop: Builds created from the develop branch, e.g. docker pull docker.io/ptr727/nxmeta:develop.
develop-stable: The develop branch's stable build, e.g. docker pull docker.io/ptr727/nxmeta:develop-stable.
develop-[version]: A develop build at a specific version, e.g. docker pull docker.io/ptr727/nxmeta:develop-6.1.3.43301.
[version]: Release version number, e.g. docker pull docker.io/ptr727/nxmeta:5.2.2.37996.

Notes:

latest and stable may be the same version if all builds are released builds.
rc and beta tags are only built when Nx publishes RC and Beta builds. They may be older than the current latest or stable builds.
One publish run covers one branch. The weekly schedule rebuilds main and picks up the latest upstream Ubuntu updates.
A push to main changing Make/Matrix.json publishes at once, so a new Nx version ships without waiting for the schedule. Only a push by the codegen App or Dependabot triggers this. A push by a person does not publish.
The develop tags are published by starting the publisher manually from develop.
Merging code or dependency updates does not republish images. The published images change only when their content changes.
See Build Process for more details.

Configuration

User accounts and directory names are based on the product variant exposed by the ${COMPANY_NAME} variable:

NxWitness: networkoptix
DWSpectrum: digitalwatchdog
NxMeta: networkoptix-metavms
WisenetWAVE: hanwha

LSIO Volumes

The LSIO images re-link various internal paths to /config.

/config : Configuration files:
- /opt/${COMPANY_NAME}/mediaserver/etc links to /config/etc : Configuration.
- /root/.config/nx_ini links to /config/ini : Additional configuration.
- /opt/${COMPANY_NAME}/mediaserver/var links to /config/var : State and logs.
/media : Recording files.

Non-LSIO Volumes

The non-LSIO images must be mapped directly to the installed paths, refer to the nxvms-docker page for details.

/opt/${COMPANY_NAME}/mediaserver/etc : Configuration.
/home/${COMPANY_NAME}/.config/nx_ini : Additional configuration.
/opt/${COMPANY_NAME}/mediaserver/var : State and logs.
/media : Recording files.

Ports

7001 : Default server port.

Environment Variables

PUID : User Id, LSIO only, optional.
PGID : Group Id, LSIO only, optional.
TZ : Timezone, e.g. America/Los_Angeles.

See LSIO docs for usage of PUID and PGID that allow the mediaserver to run under a user account and the root-tool to run as root.

Network Mode

Any network mode can be used, but due to the hardware bound licensing, host mode is recommended.

Examples

LSIO Docker Create

docker create \
  --name=nxwitness-lsio-test-container \
  --hostname=nxwitness-lsio-test-host \
  --domainname=foo.bar.net \
  --restart=unless-stopped \
  --network=host \
  --env TZ=America/Los_Angeles \
  --volume /mnt/nxwitness/config:/config:rw \
  --volume /mnt/nxwitness/media:/media:rw \
  docker.io/ptr727/nxwitness-lsio:stable

docker start nxwitness-lsio-test-container

LSIO Docker Compose

services:
  nxwitness:
    image: docker.io/ptr727/nxwitness-lsio:stable
    container_name: nxwitness-lsio-test-container
    restart: unless-stopped
    network_mode: host
    environment:
      # - PUID=65534 # id $user
      # - PGID=65534 # id $group
      - TZ=America/Los_Angeles
    volumes:
      - /mnt/nxwitness/config:/config
      - /mnt/nxwitness/media:/media
    tmpfs:
      # Keep mediaserver's Unix socket and tmp files in RAM
      - /tmp:size=1g,mode=1777

Non-LSIO Docker Compose

services:
  nxwitness:
    image: docker.io/ptr727/nxwitness:stable
    container_name: nxwitness-test-container
    restart: unless-stopped
    network_mode: host
    volumes:
      - /mnt/nxwitness/config/etc:/opt/networkoptix/mediaserver/etc
      - /mnt/nxwitness/config/nx_ini:/home/networkoptix/.config/nx_ini
      - /mnt/nxwitness/config/var:/opt/networkoptix/mediaserver/var
      - /mnt/nxwitness/media:/media
    tmpfs:
      # Keep mediaserver's Unix socket and tmp files in RAM
      - /tmp:size=1g,mode=1777

Unraid Template

Add the template URL https://github.com/ptr727/NxWitness/tree/main/Unraid to the "Template Repositories" section, at the bottom of the "Docker" configuration tab, and click "Save".
Create a new container by clicking the "Add Container" button, select the desired product template from the dropdown.
If using Unassigned Devices for media storage, use RW/Slave access mode.
Use nobody and users identifiers, PUID=99 and PGID=100.
Register the Unraid filesystems in the additionalLocalFsTypes advanced settings, see the Missing Storage section for help.

Product Information

Release Information

Advanced Configuration

mediaserver.conf Configuration: https://[hostname]:[port]/#/server-documentation
nx_vms_server.ini Configuration: https://[hostname]:[port]/api/iniConfig/
Advanced Server Configuration: https://[hostname]:[port]/#/settings/advanced
Storage Reporting: https://[hostname]:[port]/#/health/storages

Build Process

Build overview:

CreateMatrix is used to update available product versions, and to create Docker files for all product permutations.
Version.json is updated using the mediaserver Releases JSON API and Packages API.
The logic follows the same pattern as used by the Nx Open desktop client logic.
The "released" status of a build follows the same method Nx uses in isBuildPublished(). From the Releases JSON API, release_date must be greater than 0 and release_delivery_days must be 0 or greater.
Matrix.json is created from the Version.json file and is used during pipeline builds using a Matrix strategy.
Automated builds use GitHub Actions:
- Pull requests run unit tests, and a fast representative amd64 smoke build of NxMeta and NxMeta-LSIO (test-pull-request.yml). The smoke build is gated on a change under Docker/, or to Matrix.json or Version.json. A version or matrix change is covered rather than skipped. The full matrix is not built on every PR.
- Publishing runs on one branch at a time (publish-release.yml). The weekly schedule publishes main. A manual dispatch publishes whichever branch it is started from, which is how develop is published.
- A push to main that changes Matrix.json also publishes main, but only when the codegen App or Dependabot made it. A push by a person does not publish.
- Any other merge does not publish. A merge to main ships on the next weekly run, and a merge to develop ships only when someone dispatches the publisher from develop.
Version history is maintained and used by CreateMatrix such that generic tags, e.g. latest, will never result in a lesser version number, i.e. break-fix-forward only, see Issue #62 for details on Nx re-publishing "released" builds using an older version breaking already upgraded systems.

Local testing:

Run cd ./Make and ./Test.sh, the following will be executed:
- Create.sh: Creates the Dockerfiles and updates the latest version information using CreateMatrix.
- Build.sh: Builds the Dockerfiles using docker buildx build.
- Up.sh: Launch a Docker Compose stack Test.yml to run all product variants.
Ctrl-Click on the links to launch the web UI for each of the product variants.
Run Clean.sh to shutdown the compose stack and cleanup images.

Known Issues

Licensing:
- Camera recording license keys are activated and bound to hardware attributes of the host server collected by the root-tool that is required to run as root.
- Requiring the root-tool to run as root overly complicates running the mediaserver as a non-root user, and requires the container to run using host networking to not break the hardware license checks.
- Docker containers are supposed to be portable, and moving containers between hosts will break license activation.
- Nx's own nxvms-docker reference image disabled root-tool in late 2025 by setting ignoreRootTool=true in mediaserver.conf and dropping their separate root-tool container. This trades hardware-ID license enforcement for a simpler unprivileged container. NxWitness does not follow this change, because licensed deployments would lose activation. This will be revisited only if Nx publishes a clearer official position on Docker licensing without root-tool.
- Nx to fix: Associate licenses with the Cloud Account not the local hardware.
Storage Management:
- The mediaserver attempts to automatically decide what storage to use.
- Filesystem types are filtered out if not on the supported list.
- Mounted volumes are ignored if backed by the same physical storage, even if logically separate.
- Unwanted Nx MetaVMS Media directories are created on any discoverable writable storage.
- Nx to fix: Eliminate the elaborate filesystem filter logic and use only the admin specified storage locations.
Configuration Files:
- .conf configuration files are located in a static mediaserver/etc location while .ini configuration files are in a user-account dependent location, e.g. /home/networkoptix/.config/nx_ini or /root/.config/nx_ini.
- There is no value in having a server use per-user configuration directories, and it is inconsistent to mix configuration file locations.
- Nx to fix: Store all configuration files in mediaserver/etc.
External Plugins:
- Custom or Marketplace plugins are installed in the mediaserver/bin/plugins directory.
- The mediaserver/bin/plugins directory is already pre-populated with Nx installed plugins.
- It is not possible to use external plugins from a mounted volume as the directory is already in-use.
- Nx to fix: Load plugins from mediaserver/var/plugins or from sub-directories mounted below mediaserver/bin/plugins, e.g. mediaserver/bin/plugins/external
Lifetime Upgrades:
- Nx is a cloud product, free to view, free upgrades, comes with ongoing costs of hosting, maintenance, and support, it is unfeasible to sustain a business with ongoing costs using perpetual one-off licenses.
- My personal experience with Digital Watchdog and their Lifetime Upgrades and No Annual Agreements is an inflexible policy of three activations per license and you have to buy a new license, thus the "license lifetime" is a multiplier of the "hardware lifetime".
- Nx to fix: Yearly camera license renewals covering the cost of support and upgrades.
Archiving:
- Nx makes no distinction between recording and archiving storage, archive is basically just a recording mirror without any capacity or retention benefit.
- Recording storage is typically high speed low latency high cost low capacity SSD/NVMe arrays, while archival playback storage is very high capacity low cost magnetic media arrays.
- Nx to fix: Implement something akin to archiving in Milestone XProtect VMS where recording storage is separate from long term archival storage.
Image Publication:
- Nx relies on end-users or projects like this one to create and publish Docker images.
- Nx to fix: Publish up-to-date images for all product variants and release channels.
Break-Fix-Version-Forward:
- Nx product versions published via their releases API occasionally go backwards, e.g. release: v4.3 -> v5.0 -> v4.3.
- Nx supports forward-only in-place upgrades, e.g. v4.3 to v5.0, but not v5.0 to v4.3.
- Publishing generic tags, e.g. latest, using a version that regresses, e.g. v4.3 -> v5.0 -> v4.3 breaks deployments, see Issue #62 for details.
- CreateMatrix tooling keeps track of published versions, and prevents version regression of generic latest, rc and beta tags.
- Nx to fix: Release break-fix-version-forward only via release API's.

Troubleshooting

Common deployment problems and how to diagnose them.

Missing Storage

The following section will help troubleshoot common problems with missing storage.
If this does not help, please contact Network Optix Support.
Please do not open a GitHub issue unless you are positive the issue is with the Dockerfile.

Confirm that all the mounted volumes are listed in the available storage locations in the web admin portal.

Enable debug logging in the mediaserver:
Edit mediaserver.conf, set logLevel=verbose, restart the server.
Look for clues in /config/var/log/log_file.log.

E.g.

VERBOSE nx::vms::server::fs: shfs /media fuse.shfs - duplicate
VERBOSE nx::vms::server::fs: /dev/sdb8 /media btrfs - duplicate
DEBUG QnStorageSpaceRestHandler(0x7f85043b0b00): Return 0 storages and 1 protocols

Get a list of the mapped volume mounts in the running container, and verify that /config and /media are listed in the Mounts section:

docker ps --no-trunc
docker container inspect [containername]

Launch a shell in the running container and get a list of filesystems mounts:

docker ps --no-trunc
docker exec --interactive --tty [containername] /bin/bash
cat /proc/mounts
exit

Example output for ZFS (note that ZFS support was added in v5.0):

ssdpool/appdata /config zfs rw,noatime,xattr,posixacl 0 0
nvrpool/nvr /media zfs rw,noatime,xattr,posixacl 0 0
ssdpool/docker /archive zfs rw,noatime,xattr,posixacl 0 0

Mount /config is on device ssdpool/appdata and filesystem is zfs.
Mount /media is on device nvrpool/nvr and filesystem is zfs.
Mount /archive is on device ssdpool/docker and filesystem is zfs.

In this case the devices are unique and will not be filtered, but zfs is not supported and needs to be registered.

Example output for UnRaid FUSE:

shfs /config fuse.shfs rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other 0 0
shfs /media fuse.shfs rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other 0 0
shfs /archive fuse.shfs rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other 0 0

In this case there are two issues, the device is /shfs for all three mounts and will be filtered, and the filesystem type is fuse.shfs that is not supported and needs to be registered.

Log file output for Unraid FUSE:

VERBOSE nx::vms::server::fs: shfs /config fuse.shfs - added
VERBOSE nx::vms::server::fs: shfs /media fuse.shfs - added
VERBOSE nx::vms::server::fs: shfs /archive fuse.shfs - duplicate

The /archive mount is classified as a duplicate and ignored, map just /media, do not map /archive.
Alternative use the "Unassigned Devices" plugin and dedicate e.g. a XFS formatted SSD drive to /media and/or /config.

Example output for Unraid BTRFS:

/dev/sdb8 /test btrfs rw,relatime,space_cache,subvolid=5,subvol=/test 0 0
/dev/sdb8 /config btrfs rw,relatime,space_cache,subvolid=5,subvol=/config 0 0
/dev/sdb8 /media btrfs rw,relatime,space_cache,subvolid=5,subvol=/media 0 0
/dev/sdb8 /archive btrfs rw,relatime,space_cache,subvolid=5,subvol=/archive 0 0

VERBOSE nx::vms::server::fs: /dev/sdb8 /test btrfs - added
VERBOSE nx::vms::server::fs: /dev/sdb8 /config btrfs - duplicate
VERBOSE nx::vms::server::fs: /dev/sdb8 /media btrfs - duplicate
VERBOSE nx::vms::server::fs: /dev/sdb8 /archive btrfs - duplicate

In this example the /test volume was accepted, but all other volumes on /dev/sdb8 was ignored as duplicates.

Add the required filesystem types in the advanced configuration menu. Edit the additionalLocalFsTypes option and add the required filesystem types, e.g. fuse.shfs,btrfs,zfs, restart the server.

Alternatively call the configuration API directly:
wget --ask-password --user=[username] --ca-certificate=[server-cert.pem] https://[hostname]:[port]/api/systemSettings?additionalLocalFsTypes=fuse.shfs,btrfs,zfs

The mediaserver presents a self-signed certificate, which a client validating against the system trust store rejects. --ca-certificate trusts that one certificate rather than switching validation off, so export the server's certificate once and point at the file. --ask-password prompts instead of taking the password as an argument, which keeps it out of the shell history and the process list. Do not reach for --no-check-certificate here: it sends the credentials over a connection nobody has authenticated, which an active man-in-the-middle can capture.

To my knowledge there is no solution to duplicate devices being filtered, please contact Network Optix Support and ask them to stop filtering filesystem types and devices.

Questions or Issues

I am not affiliated with Network Optix, I cannot provide support for their products, please contact Network Optix Support for product support issues.
If there are issues with the Docker build scripts used in this project, please create a GitHub Issue.
Note that I only test and run nxmeta-lsio:stable in my home lab, other images get very little to no testing, please test accordingly.

Read Troubleshooting before filing an issue about missing or ignored storage, as the cause is almost always the mediaserver filesystem and device filtering described there.

3rd Party Tools

The third-party tools, libraries, and actions this project depends on.

Tool	Role
actionlint	GitHub Actions workflow linter.
AwesomeAssertions	Assertion library for .NET tests.
Codecov	Code coverage reporting service.
Create Pull Request	GitHub action that opens a pull request from workspace changes.
CSharpier	C# code formatter.
cspell	Spell checker.
Docker	Container build and runtime platform.
Docker Hub Description	GitHub action that publishes a Docker Hub repository overview.
dotnet-outdated	Outdated NuGet dependency reporter.
editorconfig-checker	Line-ending and whitespace linter.
GH Release	GitHub action that creates a release.
GitHub Actions	CI and automation runner.
GitHub Dependabot	Dependency update bot.
Husky.Net	Git hook manager for .NET.
LinuxServer	Publisher of container base images and application images.
Markdown All in One	Markdown editing extension.
markdownlint-cli2	Markdown linter.
Nerdbank.GitVersioning	Version computation from git height.
s6-overlay	Process supervisor and init system for containers.
Serilog	Structured logging library for .NET.
System.CommandLine	Command line parsing library for .NET.
Ubuntu	Linux distribution.
xUnit.Net	Test framework for .NET.

License

Licensed under the MIT License

Name		Name	Last commit message	Last commit date
.config		.config
.github		.github
.husky		.husky
.vscode		.vscode
CreateMatrix		CreateMatrix
CreateMatrixTests		CreateMatrixTests
Docker		Docker
Make		Make
Samples		Samples
Unraid		Unraid
.dockerignore		.dockerignore
.editorconfig		.editorconfig
.editorconfig-checker.json		.editorconfig-checker.json
.gitattributes		.gitattributes
.gitignore		.gitignore
.markdownlint-cli2.jsonc		.markdownlint-cli2.jsonc
AGENTS.md		AGENTS.md
ARCHITECTURE.md		ARCHITECTURE.md
CLAUDE.md		CLAUDE.md
CODESTYLE.md		CODESTYLE.md
GOVERNANCE.md		GOVERNANCE.md
HISTORY.md		HISTORY.md
LICENSE		LICENSE
NxWitness.code-workspace		NxWitness.code-workspace
NxWitness.slnx		NxWitness.slnx
OPERATIONS.md		OPERATIONS.md
README.md		README.md
WORKFLOW.md		WORKFLOW.md
codecov.yml		codecov.yml
cspell.json		cspell.json
global.json		global.json
host-tools.json		host-tools.json
version.json		version.json

Latest commit

History

Folders and files

Repository files navigation

NxWitness

Build and Distribution

Build Status

Releases

Release Notes

Getting Started

Table of Contents

Products

Overview

Introduction

Base Images

LinuxServer

Installation

Configuration

LSIO Volumes

Non-LSIO Volumes

Ports

Environment Variables

Network Mode

Examples

LSIO Docker Create

LSIO Docker Compose

Non-LSIO Docker Compose

Unraid Template

Product Information

Release Information

Advanced Configuration

Build Process

Known Issues

Troubleshooting

Missing Storage

Questions or Issues

3rd Party Tools

License

About

Topics

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages