The portnox-autoupdate container automatically updates other Portnox Docker containers running on the same Docker host to their latest versions, as soon as they are available. Without it, you need to remove and redeploy your containers manually every time a new version comes out.
The container needs access to the Docker socket on its host, since it has to inspect and recreate the other Portnox containers running there, so it can only update containers on the same host, and only one instance can run per host. Because of this, it can only run on an on-premises Docker host where you control the Docker engine directly. It cannot run in cloud container services, since these do not expose the Docker socket, so you have to manually update any containers running in your own private cloud services.
You need your organization ID and an API token. To find your organization ID, look at your self-onboarding portal URL, for example, if the URL is https://user-registration.portnox.com/b2973887-1274-45c4-91d0-4a342a861c76, the organization ID is the part after the domain: b2973887-1274-45c4-91d0-4a342a861c76. To get an API token, go to Settings > Profile Settings > ACCOUNT SETTINGS in Portnox Cloud, and in the CLOUD API TOKENS section, click on Generate token. Give the token a name, choose whether it expires, and copy the generated value. Then run the container:
sudo docker run --restart=always -d --name portnox-autoupdate \
-v /var/run/docker.sock:/var/run/docker.sock \
-v portnox-autoupdate-logs:/app/logs \
-e AUTO_UPDATE_ORG_ID=<org_id> \
-e AUTO_UPDATE_PORTNOX_API_TOKEN=<api_token> \
portnox/portnox-autoupdate:latest
Automatic update checks run once per day, at a random time between 1:00 AM and 2:00 AM local container time. Containers are updated one at a time, and portnox-autoupdate always updates itself last.
For full documentation, see: docs.portnox.com.
Content type
Image
Digest
sha256:1a21fdba5…
Size
42 MB
Last updated
3 months ago
docker pull portnox/portnox-autoupdatePulls:
26
Last week