Installation on Docker


This install option is specifically for:

  • Docker running on a Linux operating system.
  • those wanting to perform a clean install

The installation media is provided in com.castsoftware.imaging.all.docker and comprises an installation script and various configuration files. All Docker images are pulled direct from during the installation.

The following components are provided as Docker images:

  • CAST Imaging Services including:
    • CAST Dashboards
    • Database instance additional remote database instances can also be declared post install
  • CAST Imaging Viewer
  • CAST Imaging Node including:
    • CAST Imaging Core

The installation script is completely flexible and allows you to install in whichever way suits your environment:

  • All components on one machine in a single Docker instance
  • Components distributed across multiple machines in separate Docker instances (load balancing mode - this is the recommended installation method)

This flexibility is achieved by running the installation script with specific install commands:

Command Components installed Containers created in Docker
  • All components - one machine installation scenario. If you choose this option, you must ensure that your machine has sufficient resources to run all components: 16GB RAM absolute minimum, 32GB highly recommended.
  • auth-service
  • aip-console-v3
  • dashboards
  • gateway
  • keycloak-v3
  • control-panel
  • v3-postgres
  • aip_node_v3
  • CAST Imaging Services
  • CAST Dashboards
  • Database instance
  • auth-service
  • aip-console-v3
  • dashboards
  • gateway
  • keycloak-v3
  • control-panel
  • v3-postgres
  • CAST Imaging Viewer
  • CAST Imaging Node (includes CAST Imaging Core)
  • aip_node_v3

Current limitations

Unsupported technologies

The following technologies are not supported:

  • C/C++ (will be supported in a future release)
  • EGL
  • FLEX
  • Microsoft VisualBasic
  • Oracle Forms/Reports
  • PeopleSoft
  • SAP ABAP (will be supported in a future release)
  • SAP BusinessObjects
  • SAP PowerBuilder
  • Siebel
  • Swift (iOS)

Unsupported features

The Reference Finder (available via Application > Configuration > Advanced Configuration > Reference Finder) is not supported.


See Requirements .

Step 1 - Determine your installation method

  • If you are installing all components on one machine, connect to the machine and proceed to Step 2 . Ensure that your machine has sufficient resources to run all components: 16GB RAM absolute minimum, 32GB highly recommended.

  • Alternatively, if you want to install the components on multiple machines, you need to determine which machine will run the CAST Imaging Services (imaging-services) components because these components must be installed first before any others. Connect to this machine and then proceed to Step 2 .

Step 2 - Download the installation media

Download the latest release of the installer using curl and unzip it anywhere on your local disk, where:

curl -O -J "" -H "x-nuget-apikey: <api-key>" -H "accept: application/octet-stream"

The following files/folders will be visible:

  • cast_imaging_node (folder)
  • cast_imaging_services (folder)
  • cast_imaging_viewer (folder)
  • (file)
  • configuration.conf (file)

Step 3 - Configure your installation

Locate the configuration.conf file at the root of the unzipped files and open it in a text editor such as nano or vi. Change only the following:

  • IMAGING_SERVICES_HOSTNAME: configure the machine’s FQDN (fully qualified domain name) or its static IP address - run the command hostname -f or hostname -i to determine this
  • IMAGING_NODE_VOLUME_xxx: set the path of the required data folders:
    • use local folders if you are installing all components on one machine
    • use a mapped network share drive or use a UNC path of the network share if you are installing components on multiple machines, for example: //machine/shared/delivery
  • IMAGING_VIEWER_VOLUME_SHARED_FOLDER: set the path of the folder which will be used by the CAST Imaging Viewer component for its configuration files. This should be a folder on the local machine, but should NOT exist already

For example for a multiple machine scenario:

Step 4 - Make files executable

Run the following commands to ensure that the installation scripts are executable:

chmod +x

If you are installing the CAST Imaging Viewer component on this machine (via the all or imaging-viewer commands), then you must also run the following commands, where:

  • <path>: points to the grandparent folder of the folder defined for the variable IMAGING_VIEWER_VOLUME_SHARED_FOLDER. For example, if you have set IMAGING_VIEWER_VOLUME_SHARED_FOLDER=/home/CAST/imaging-viewer then you should run chmod -R u+rwx /home
  • <user>: set to the username of the user that will run the installation script
chmod +x cast_imaging_viewer/imagingsetup
chmod -R u+rwx <path>
chown <user>:<user> -R <path>

Step 5 - Run the installation

Scenario 1 - Install all components on one machine

Run the following command:

./ all

On completion, check the status of the various Docker containers - there should be 12 in total:

docker ps

Scenario 2 - Install components on multiple machines

On each machine on which you want to install a component, ensure that you follow Step 2 , Step 3 and Step 4 , i.e.:

  • download and unzip the installation media on each machine on which you want to install a component
  • ensure the configuration.conf file on each machine is identical
  • ensure the relevant files are executable

Then run the appropriate installation command on each machine for the component you would like to install. Ensure that the imaging-services component is always installed first and is completed before any other components are installed:

./ imaging-services
./ imaging-viewer
./ analysis-node

On completion, check the status of the various Docker containers:

docker ps
Command No. of containers
imaging-services 7
imaging-viewer 4
analysis-node 1

Step 6 - Post install tasks

Set permissions on persistent volumes

For each CAST Imaging Node Service (analysis-node) you have installed (including where you have used the all command) you must execute the following command on each machine to ensure that the root user has access to the persistent volumes shared with the CAST Imaging Node container, where:

  • <root_data_folder>: points to the root of the data folder. For example, if you have set IMAGING_NODE_VOLUME_DELIVERY_FOLDER=//machine/shared/delivery then you should run chmod -R u+rwx //machine/shared
chown -R 0:0 <root_data_folder>

Open firewall ports

To ensure that:

  • your users can access all CAST Imaging resources in their browser
  • CAST Imaging components can communicate correctly in a multi-machine installation scenario

…you should ensure that port 8090 (TCP) is opened inbound on the machine hosting the imaging-services component (this is also valid for one machine installations using the all option).

Step 7 - Initial start up configuration

When the install is complete, browse to the URL below and login using the default local admin/admin credentials:


You will be prompted to configure:

  • your licensing strategy. Choose either a Named Application strategy (where each application you onboard requires a dedicated license key entered when you perform the onboarding), or a Contributing Developers strategy (a global license key based on the number of users):

License key

  • CAST Extend settings (API key/proxy):

CAST Extend settings

As a final check, browse to the URL below and ensure that you have at least one CAST Imaging Node Service, the CAST Dashboards and the CAST Imaging Viewer components listed:



Step 8 - Configure authentication

Out-of-the-box, CAST Imaging is configured to use Local Authentication via a simple username/password system. Default login credentials are provided (admin/admin) with the global ADMIN profile so that installation can be set up initially.

CAST recommends configuring CAST Imaging to use your on-premises enterprise authentication system such as LDAP or SAML Single Sign-on instead before you start to onboard applications. See Authentication for more information.

What is installed?

The following Docker containers will be created and are set to start automatically:

auth-service aip-console-v3 dashboards gateway keycloak-v3 control-panel


Command Container (Port)
  • v3-postgres (2285)
  • gateway (8090)
  • aip-console-v3 (8091)
  • auth-service (8092)
  • keycloak-v3 (8096)
  • dashboards (8097)
  • control-panel (8098)
  • aip_node_v3 (8089)

What about analysis data storage?

All analysis data will be stored in the folders you defined in the configuration.conf file.

What happens if a container does not start?

If a container fails to start, run the following command to display the container logs - this will give an indication of what may have gone wrong:

docker logs <container_name>

Uninstall process

Run the following command to stop all running containers on your Docker instance:

docker stop $(docker ps -a -q)

Now run the following commands to completely remove all components:

#Remove all unused local volumes. Unused local volumes are those which are not referenced by any containers
docker volume prune

#Remove all unused containers, networks, images (both dangling and unreferenced)
docker system prune -a 

Finally, delete the installer ZIP file, the unzipped folder and any installation folders.

What is not removed?

  • Analysis data files in the folders defined by the variables IMAGING_NODE_VOLUME_xxx
  • Any application schemas on additional remote database instances you have been using.

If you intend to perform a clean install on the same machine(s) you should ensure that these items are removed first.