Skip to content

Registry access

Walter On-Prem 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
  • access to supported Walter releases
  • 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:<supported-release>

If the image pull succeeds, the installer should also work.

The public installer defaults to the latest stable manifest release:

curl -fsSL https://onprem.walterops.com/install/install-walter.sh | bash

If Docker is not already logged into ghcr.io, the installer prompts for the GHCR username and token Walter provided separately and then runs docker login for you.

If you want to pin a release explicitly:

curl -fsSL https://onprem.walterops.com/install/install-walter.sh | \
  bash -s -- --to <supported-release>

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:<supported-release>

Credential handling

  • Keep customer tokens separate per environment or per customer
  • Rotate tokens if they are copied into chat, tickets, or email
  • Prefer pinned releases or manifest targets over latest