Skip to content

Container Registries

Privitty Edge images are published to Docker Hub and GitHub Container Registry (GHCR) as multi-arch manifests.

Available tags

Tag Contents
latest Daemon + CLI
latest-viewer Daemon + CLI + privitty-viewer
<version> Release version (e.g. 1.2.0)
<version>-viewer Release with viewer

Pull commands

docker pull privitty/edge:latest
docker pull privitty/edge:1.2.0
docker pull privitty/edge:latest-viewer

docker pull ghcr.io/privitty/edge:latest
docker pull ghcr.io/privitty/edge:1.2.0
docker pull ghcr.io/privitty/edge:latest-viewer

Supported platforms

All tags are multi-arch manifests:

Platform Typical hardware
linux/amd64 x86 gateways, cloud VMs, MEC nodes
linux/arm64 Raspberry Pi 4, NVIDIA Jetson, Advantech, Dell ARM gateways
linux/arm/v7 ARMv7 embedded gateways (Moxa, legacy industrial hardware)

Docker automatically selects the correct architecture:

docker inspect privitty/edge:latest --format '{{.Architecture}}'

List all platforms in a manifest:

docker buildx imagetools inspect privitty/edge:latest

Image characteristics

Property Value
Base image scratch (empty — no OS)
Linking Fully static musl binary
User Non-root (privitty, UID 1000)
Exposed port 7200
Health check Built-in (privitty-edge health)

Pinning versions in production

Use an explicit version tag rather than latest:

# docker-compose.yml
image: privitty/edge:1.2.0

Or with digest pinning for maximum reproducibility:

docker pull privitty/edge:1.2.0
docker inspect privitty/edge:1.2.0 --format '{{index .RepoDigests 0}}'

Private registry mirroring

For air-gapped or enterprise registries, pull from upstream and re-tag:

docker pull privitty/edge:1.2.0
docker tag privitty/edge:1.2.0 registry.internal.example/privitty/edge:1.2.0
docker push registry.internal.example/privitty/edge:1.2.0

Repeat for each required platform or mirror the full manifest with docker buildx imagetools create.