To simplify deployment, Ansys HPC Platform Core Services are delivered via containers. A container bundles an application’s code with all related configuration files, libraries, and dependencies required for the application to run. As containers are not tied to any specific environment, they are lightweight and portable, making deployment quick, consistent, and reliable in any environment.
To run containers, a container engine is required. Docker is used for this purpose.
Ansys provides Docker files that contain the configuration instructions for building the Ansys Docker images. An image defines an executable package of software. You use docker-compose commands to build images from the Docker files and then create and start containers based on the images. Containers are running instances of images.

Ansys ships relevant configuration files for Docker Compose and Kubernetes (docker compose, Helm respectively). All configuration data such as base images, environment, networking, and used ports are contained within these configuration files.
Third-Party Containers
When you deploy Ansys HPC Platform Core Services, the following third-party services are downloaded from third-party container registries:
Service | Used for | Container information | Container pull |
---|---|---|---|
Keycloak | Identity and Access Management (IAM) | https://quay.io/repository/keycloak/keycloak?tab=info | quay.io/keycloak/keycloak:22.0.5 |
Keydb | Database | https://hub.docker.com/r/eqalpha/keydb | eqalpha/keydb:alpine_x86_64_v6.3.3 |
Influxdb | Database | https://hub.docker.com/_/influxdb | influxdb:1.8.10 |
Postgres | Database | https://hub.docker.com/_/postgres | postgres:16.0 |
Traefik | Security, networking gateway | https://hub.docker.com/_/traefik | traefik:2.9 |