Containerized TERR service
When you install the TERR service on a Linux computer, by default, it is configured to use a Docker® container. A containerized TERR service is available only for Linux installations.
- If you have not yet installed the TERR service, install Docker first, and then install the TERR service.
- If you have already installed the TERR service before installing Docker, then stop the TERR service, install Docker, set the configuration to use Docker, and then restart the TERR service.
The primary benefit of installing and using the TERR service in a container is that it operates the service in a "sandbox", so the TERR engine does not have access to the host file system. (For more information about script and data function trust, see the TIBCO Spotfire Analyst User's Guide). Running the TERR service in a container results in negligible performance impact.
The only container framework with which we developed and tested the TERR service is Docker. We do not provide Docker with the base installation; however, you must have Docker installed for the TERR service to work properly out of the box. The service downloads and builds a default Docker image based on CentOS 8 from Docker Hub. While you cannot modify the image we provide, you can build and use a different Docker image if you have different configuration requirements. This section contains a few examples of specifying different Docker images. Alternatively, check Docker Hub for an image that might work for you.
You can export and change the configuration options to build and install a customized image. See Configuring the TERR service for more information. The properties to change in the configuration are the following.
After you install and configure both the container and the TERR service, you can start the service. When the service starts, containers are created as needed.
use.engine.containers
to
FALSE
to disable the container option.
- Configuring a custom Docker image on a node with internet access
If you have access to the internet, then you can build a Docker image for your TERR service, referencing it by its name and tag. - Configuring a custom Docker image on a node with no internet access
If your node manager does not have external access to the internet, then you can create a Docker image on an internet-enabled computer, and then transfer it to your node manager. - Configuring a custom startup script to build a custom Docker image
You can provide a startup script that is installed and configured on your Spotfire Server to build a custom Docker image for your TERR service. - Pulling a custom Docker image from an authenticated repository
You can create a custom start script to configure the TERR service to log in to a remote authenticated repository and pull a custom Docker image.
- Configuring a custom Docker image on a node with internet access
If you have access to the internet, then you can build a Docker image for your TERR service, referencing it by its name and tag. - Configuring a custom Docker image on a node with no internet access
If your node manager does not have external access to the internet, then you can create a Docker image on an internet-enabled computer, and then transfer it to your node manager. - Configuring a custom startup script to build a custom Docker image
You can provide a startup script that is installed and configured on your Spotfire Server to build a custom Docker image for your TERR service. - Pulling a custom Docker image from an authenticated repository
You can create a custom start script to configure the TERR service to log in to a remote authenticated repository and pull a custom Docker image.