Updating your Remote Engine Gen2 with the new connectors image

Procedure

Go to the Remote Engine Gen2 installation directory.
Edit the remote-engine.[sh|bat] executable:
1. Look for the line docker-compose pull and comment out this line. This line makes the script check to see if the latest docker images should be pulled and could potentially overwrite your custom connectors image.
2. Save your changes.

Open the following file to edit it:

default/.env if you are using the engine in the AWS USA, AWS Europe, AWS Asia-Pacific or Azure regions.

eap/.env if you are using the engine as part of the Early Adopter Program.

Look for the CONNECTORS_IMG line and update its value by pasting the connectors image ID you generated previously.

Example

TALEND_DIR=.
LOG_LEVEL=INFO

# The configuration below should not be changed
COMPONENTS_IMG=talend/component-server:1.x.x
COMPONENTS_MEM=1024M
SRE_AGENT_IMG=talend/remote-engine-agent:0.xx
PREVIEW_RUNNER_IMG=talend/data-streams-ee-previewrunner:1.x
LIVY_IMG=talend/livy:x.x
LIVY_MEM=1024M
AUTOHEAL_IMG=willfarrell/autoheal:v0.x.x
CONNECTORS_IMG=e761f26e4adb:20191206151130452                        <--------------------- Update connectors image name here 
COMPONENTS_VAULT_PROXY_IMG=talend/component-server-vault-proxy:1.x.x
HDFS_TOOL_IMG=talend/hdfs-tool:0.x
VAULT_AGENT_IMG=vault:1.x.x

Save your changes.

Restart the Remote Engine Gen2.

Results

The new Docker image is retrieved and you are now able to use your new connector or processor in Talend Cloud Pipeline Designer using the updated Remote Engine Gen2.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here