CAST provides a single provides Docker image images for Microsoft Windows and Linux (available in Docker hub) that includes the CAST AIP Components listed below. It has been implemented to facilitate CAST AIP deployment. The image is images are deployed via the CAST AIP Docker Installer (an interactive batch script) in a unique container containers created by the installer and you can therefore install multiple CAST AIP containers in the Docker environment - for example to install multiple AIP Nodes on the same server within Docker.
|Docker for Microsoft Windows||Docker for Linux|
AIP Console (front end) - including embedded CAST Dashboards
|AIP Console (front end) - including embedded CAST Dashboards|
|AIP Core (currently only for Management/Engineering - DashboardCAST Dashboards, not CAST Imaging)||-|
|CAST Extend local server||-|
CAST Health / Engineering / Security Dashboards - in standalone mode. Available in ≥ 1.0.2. Provided as a separate install script in a separate container.
Installation is flexible and you can install all these components or different combinations of them within the container created by the installer:
Docker for Microsoft Windows
- Deploy AIP Console (front end)
- Choose to store the AIP Console persistence database in a specific location on the server, or leave it with the Docker container
- Deploy CAST Dashboards in standalone mode in an additional dedicated container
Which releases of CAST AIP components are provided in the image?
The Docker image images provided by CAST will contain the most recent "funcrel" releases of each component where possible. Images are updated as soon as new releases of components are shipped. You can inspect the content of the images via Docker hub (Docker ID account required). The "latest" tag contains the most recent release:
- Microsoft Windows image for Console/AIP Node/AIP Core/Extend Proxy: https://hub.docker.com/r/castaip/windows_pack/tags?page=1&ordering=last_updated
- Linux image for Console/AIP Node/AIP Core/Extend Proxy: https://hub.docker.com/r/castaip/linux_pack/tags?page=1&ordering=last_updated
- Linux image for standalone Dashboards: https://hub.docker.com/r/castaip/dashboards_linux/tags?page=1&ordering=last_updated
See CAST AIP Docker Installer - Release Notes.
|Host Operating System|
See the Docker Desktop for Windows system requirements: https://docs.docker.com/docker-for-windows/install/#system-requirements
Docker Desktop for Windows - latest version recommended, or one that provides:
16GB RAM (minimum) for the host server. Note that by default, a container has no resource constraints and can use as much of a given resource as the host’s kernel scheduler allows. Please consult https://docs.docker.com/config/containers/resource_constraints/ for more information.
|Storage||25GB (minimum) free storage: SSD with SATA interface recommended. An installation of all components is currently approximately 14GB - however, if your data resides within the Docker container, then you will need additional storage.|
|CAST Storage Service / PostgreSQL instance|
The Docker image does not contain a CAST Storage Service/PostgreSQL instance for the analysis data, therefore if you are installing the AIP Node/AIP Core image (Docker for Windows only) you must install an instance on the current server (if the server is powerful enough) or on a dedicated server (recommended). The server on which Docker Desktop is installed and more specifically the container in which AIP Core/AIP Node is deployed, must be able to connect to this CAST Storage Service/PostgreSQL instance. Make sure that the configuration file pg_hba.conf in your CAST Storage Service/PostgreSQL instance is correctly configured to meet this requirement.
|Access to Docker Hub||The Docker image is images are hosted on https://hub.docker.com/, therefore the server on which you are performing the installation must have internet access to this URL.|
If the installer detects an existing container created by CAST in the Docker environment, the installer will prompt whether to remove these existing containers. The default action is to remove all existing containers:
If you choose to retain the existing containers, the installer will choose a new unique container name for the new installation (or you can choose a custom name):
Accessing files within the Docker container