Docker evaluation
Docker images are primarily artifacts for the Kubernetes operator and Helm installers. Use them for image review, scanning, and limited local evaluation.
Raw Docker containers are not the recommended production deployment model. Use operators or Helm for production.
Canonical image names
Pull release-approved images from the authenticated Graph registry.
| Product area | Image |
|---|---|
| Graph Studio | artifacts.altair.com/graph-docker/anzo |
| Graph Lakehouse database | artifacts.altair.com/graph-docker/anzograph-db |
| Graph Lakehouse frontend | artifacts.altair.com/graph-docker/anzograph-frontend |
| Graph Lakehouse all-in-one | artifacts.altair.com/graph-docker/anzograph |
| Distributed Unstructured leader | artifacts.altair.com/graph-docker/anzo-microservices-leader |
| Distributed Unstructured worker | artifacts.altair.com/graph-docker/anzo-unstructured-worker |
Sign in and create an access token as described in Prerequisites before pulling an image.
docker pull artifacts.altair.com/graph-docker/anzo:<tag>
docker pull artifacts.altair.com/graph-docker/anzograph-db:<tag>
docker pull artifacts.altair.com/graph-docker/anzograph-frontend:<tag>
Docker Hub compatibility images
Docker Hub cambridgesemantics images are compatibility references during the
migration. Confirm that the required release tag is available before using either
location; use the Graph registry for new examples and installations.
| Product area | Compatibility image |
|---|---|
| Graph Studio | docker.io/cambridgesemantics/anzo |
| Graph Lakehouse database | docker.io/cambridgesemantics/anzograph-db |
| Graph Lakehouse frontend | docker.io/cambridgesemantics/anzograph-frontend |
| Graph Lakehouse all-in-one | docker.io/cambridgesemantics/anzograph |
Use the same release-approved tag when comparing the two locations.
Local Graph Studio evaluation
A single-container Graph Studio evaluation can be useful for local testing. It requires customer-provided activation material and must not use sample licenses, fixed server IDs, or weak passwords.
Minimum flow:
- Create local data, log, activation, and startup directories.
- Create an
init.jsonwith your own administrator password, server ID, and license material. - Start the image with bind mounts for activation, startup, data, and logs.
- Open the HTTPS endpoint in a browser.
- Delete the container and local directories when done.
Keep detailed Docker evaluation procedures separate from production installation runbooks.