Skip to content

Registry access

Walter self-hosted images are distributed through GitHub Container Registry at ghcr.io/matchylabs/walter.

What operators receive

Each customer receives these values separately from the public docs:

  • a GHCR username
  • a GHCR token
  • an approved Walter image tag
  • a Walter license key

The docs site intentionally does not embed customer-specific credentials.

Validate access manually

If you want to verify registry access before running the installer:

echo "<provided-token>" | docker login ghcr.io -u <provided-username> --password-stdin
docker pull ghcr.io/matchylabs/walter:YOUR_WALTER_VERSION

If the image pull succeeds, the one-command installer should also work.

The public installer expects the Walter image tag explicitly:

WALTER_IMAGE=ghcr.io/matchylabs/walter:YOUR_WALTER_VERSION
curl -fsSL https://onprem.walterops.com/install/install-walter.sh | \
  bash -s -- --host 192.168.1.50 --image "$WALTER_IMAGE"

Podman

Podman uses the same credentials and image path:

echo "<provided-token>" | podman login ghcr.io -u <provided-username> --password-stdin
podman pull ghcr.io/matchylabs/walter:YOUR_WALTER_VERSION

Credential handling

  • Keep customer tokens separate per environment or per customer
  • Rotate tokens if they are copied into chat, tickets, or email
  • Prefer pinned tags such as YOUR_WALTER_VERSION over latest