If you are running Twingate Connectors as containers in Docker, AWS ECS, or Azure Container Instances, the instructions specific to each environment below cover how to upgrade Connectors. Please keep in mind the best practices for upgrading detailed in Upgrading Connectors to avoid downtime for your users.

See the Linux Docker deployment documentation for more information on deploying the Twingate Connector in a Linux Docker container.

Checking the Connector Version

If you’d like to check the currently running version of a Connector in a Docker container, you can do so using the following command:

 Copydocker exec twingate-connector ./connectord --version

In the above example, twingate-connector represents the name of the Connector container.

The latest build version number and other update notes are available in the Connector Release Notes.

Linux: Command line / EC2 / VM

The following command can be used to upgrade running Connectors that have been deployed on a host using the Docker CLI. The script automates:

• Pulling the latest Connector image (twingate/connector:1)
• Comparing any running containers to the latest image
• Stopping any out of date containers, deleting them, and restarting them with the same environment variables and the latest image

 Copycurl -s https://binaries.twingate.com/connector/docker-upgrade.sh | sudo nohup sudo bash

AWS Elastic Container Service (ECS)

In order to upgrade a running ECS Connector service, it needs to be restarted with the “Force new deployment” option selected. You can either do this via the AWS Management Console or with the AWS CLI.

Management Console

• Select the name of the running Connector service in your ECS cluster and choose “Update”.
• Select the “Force new deployment” option, then “Skip to review”.
• Click “Update Service”.

The service will automatically restart and pull the latest image. Note: the image that is pulled depends on the ECS task definition attached to the ECS service. Our recommended task definition uses a tag that will pull newer versions when available, but if you have modified the task definition, this behavior may be different in your case.

AWS CLI

The command below will force a new deployment of your running ECS Service. Note that you need the name of the ECS Service, Cluster name, and AWS region to run the command.

 Copyaws ecs update-service --region <REGION> --cluster <CLUSTER_NAME> --service <SERVICE_NAME> --force-new-deployment

Azure Container Instance

You can upgrade any Connectors running as a container instance on Azure with the following CLI command. This will automatically download the latest image.

You will need the container name and Resource Group name to run the command.

 Copyaz container restart --name <CONTAINER_NAME> --resource-group <RESOURCE_GROUP>

Manual steps

To manually upgrade a connector using the Docker command line, the following steps will pull the latest Connector image. Note: you will need to reprovision the Connector in the Twingate Admin console since this method does not preserve the authentication tokens for the running Connector.

 Copydocker ps
# Copy either the container ID or name
docker container rm -f [ container ID or name ]
docker image rm -f twingate/connector

# Obtain a new Docker run command from the Twingate admin console by reprovisioning the connector
docker run ...