Managing KTranslate Container Versions

Managing KTranslate Container Versions

Problem

The default Docker commands will pull the latest release every time you start the container. There are scenarios where you might want to run an older release or pin your environment to a specific version.

Solution

You can find older releases of the container on Docker Hub.

The same container image may be available under several tags. For example, the newest stable release is available from both the v2 and latest tags.

To control which release you run, take the following docker run example:

docker run -d --name ktranslate-SNMP --restart unless-stopped --pull=always -p 162:1620/udp \
-v `pwd`/snmp-base.yaml:/snmp-base.yaml \
-e NEW_RELIC_API_KEY=$YOUR_LICENSE_KEY \
kentik/ktranslate:v2 \
  -snmp /snmp-base.yaml \
  -nr_account_id=$YOUR_ACCOUNT_ID \
  -metrics=jchf \
  -tee_logs=true \
  -service_name=SNMP \
  -snmp_discovery_on_start=true \
  -snmp_discovery_min=180 \
  nr1.snmp

Remove --pull=always and change the container tag from v2 to the tag of the release you want to use:

docker run -d --name ktranslate-SNMP --restart unless-stopped -p 162:1620/udp \
-v `pwd`/snmp-base.yaml:/snmp-base.yaml \
-e NEW_RELIC_API_KEY=$YOUR_LICENSE_KEY \
kentik/ktranslate:kt-2023-02-28-4294815650 \
  -snmp /snmp-base.yaml \
  -nr_account_id=$YOUR_ACCOUNT_ID \
  -metrics=jchf \
  -tee_logs=true \
  -service_name=SNMP \
  -snmp_discovery_on_start=true \
  -snmp_discovery_min=180 \
  nr1.snmp