Lansweeper Network Discovery for Unraid

Unofficial Docker image and Unraid Community Apps template that runs the Lansweeper Network Discovery Hub and IT Sensor in one container.

The image contains no redistributed Lansweeper files. At build time it pulls the official lansweeper-network-discovery-hub and lansweeper-network-discovery-it-sensor packages from Lansweeper's signed apt repository (https://download.lansweeper.com/debian). The repository's public signing key is in keys/ (taken from Lansweeper's lansweeper-repository package).

How it works

• The packages' install scripts assume systemd, so they are not run. rootfs/usr/local/bin/entrypoint.sh does the same setup: it renders appsettings.json from the template, generates hub.ini and the sensor ID, and writes the linking code and hub code files.
• The apps keep their state next to their binaries, so /config/hub and /config/it-sensor hold both. When the image version changes, the new binaries are copied over and the state files are kept, just like an apt upgrade.
• Both processes run under a small supervisor with tini as PID 1. Their logs go to /config/*/logs and to the container log.

Layout of /config

Environment

Run manually

docker build -t lansweeper-network-discovery .
docker run -d --name lansweeper --network host \
  --cap-add NET_RAW --cap-add NET_ADMIN \
  -e LINKING_CODE=xxxxx \
  -v /mnt/cache/appdata/lansweeper-network-discovery:/config \
  lansweeper-network-discovery

Then open https://<server>:59525/. The certificate is self-signed.

First login

The Hub only lets you set the initial admin password from the server itself (localhost). While no password is set, the container relays SETUP_PORT (59526) to the Hub over loopback. Open https://<server>:59526/ once and set the password. The container closes the port as soon as the Hub records the password (AuthOptions.ChangePasswordOnLogin turns false). After that, log in at https://<server>:59525/.

Until the password is set, anyone on your network who reaches the setup port could set it, as with most first-run setup pages. Set SETUP_PORT=0 to turn the relay off. After AuthenticationTool reset, restart the container to reopen the setup port.

Unraid

The Community Applications template lives in 007darkmatter5/unraid-templates as templates/lansweeper-network-discovery.xml. The template's icon is served from this repo at docs/icon.png.

The workflow publishes ghcr.io/007darkmatter5/lansweeper-network-discovery, and it rebuilds daily when Lansweeper releases a new version. The package must be public for Unraid to pull it.

Notes

• Networking: use host (or br0 with its own IP). On a bridge network, discovery can't see the LAN.
• appdata: the Hub uses SQLite (hub.db). If you see locking errors on /mnt/user, use a pool path such as /mnt/cache/appdata/....
• The container runs as root with only NET_RAW and NET_ADMIN added. Inside the container this replaces the packages' setcap and sudoers setup.
• amd64 only, because Lansweeper publishes amd64 packages only.
• Locked out of the web UI: run docker exec -w /config/hub <container> ./AuthenticationTool reset (the tool also has enable and disable commands).
• The sensor scans the subnets of every host interface, including Tailscale (100.x). Limit the scan ranges in the Hub UI if you don't want that.
• There's no systemd in the container, so /usr/local/bin/systemctl is a no-op stand-in. The sensor only uses it to list the host's services.