Setting up the Security CLI Docker Image
To build the Security CLI Docker image necessary to support ThingWorx Docker, perform the following actions:
Make sure the required binaries are staged and available for the build process.
Modify the build.env variable file with appropriate values.
Required Files
The following files must be present in the staging folder.
The OpenJDK - Amazon Coretto 11.x.x file obtained from Amazon Web Services or the Java JDK version 11 archive file obtained from Oracle.
If you want to use some other image as a base, make the required changes in dockerfiles\ignite\Dockerfile
Example files:
1. jdk-11.x.x-linux-x64.tar.gz
2. amazon-corretto-11.x.x-linux-x64.tar.gz
Save this file into the staging folder and make sure the JAVA_VERSION and JAVA_ARCHIVE variables in the build.env file are correct.
ThingWorx Security Tool Archives
Download from the PTC Software Downloads site alongside this Dockerfile release.
Save these files into the staging folder and make sure the SECURITY_TOOL_ARCHIVE variable in the build.env file are correct.
Template Processor Archive
A tool provided by PTC to both parse templates inside the Docker container when it is starting to provide variables and format configuration files based on the running environment.
Example File:
Make sure this file in the staging folder matches the TEMPLATE_PROCESSOR_ARCHIVE variable in the build.env file.
build.env Variable
The build.env file contains a list of variables that you must set. The following variables must be set:
Variable Name
The file name of the Java archive as it exists in the staging folder.
The version of the Security Tool library
The Security Tool Library name as it exists in the staging folder.
The version of the template-processor archive as it exists in the staging folder.
Staging Files
You must place the required files for building the Docker images in the staging folder that is part of this release. The staging folder should already contain a base platform-settings.json file.
Was this helpful?