Core Update

Keep the Linknesis Core up to date with automatic checks, manual triggers, or the host-side updater.

Overview

The Core is distributed as a Docker image from linknesis.com:5000/linknesis-core. Updates are delivered through release channels:

  • stable - recommended for production environments.
  • beta - preview releases for testing. On this channel the Core and webhook sender run with debug logging enabled.

The running Core version is shown in the Web GUI and exposed via GET /api/system/version.

Automatic updates

The installer enables a systemd timer that runs linknesis-updater every 12 hours. The Core checks the configured update channel manifest daily; when a newer version is available and Core Update is enabled in Settings, the Core writes an update request. The updater then:

  1. Backs up the current .env file.
  2. Updates CORE_IMAGE_TAG to the new version.
  3. Pulls the new image from the registry.
  4. Recreates the Core and Webhook Sender containers.
  5. Restarts Nginx so it resolves the new Core container.
  6. Health-checks the Core and rolls back automatically on failure.

To verify the timer is active:

sudo systemctl status linknesis-updater.timer
sudo journalctl -u linknesis-updater -f

Manual update from the GUI

  1. Open Settings > Core Update.
  2. Select the desired channel (stable or beta).
  3. Click Check for updates to see if a newer version is available.
  4. Click Update now to start the update immediately.
  5. The UI shows live progress until the Core restarts.

Manual update from the command line

You can also run the updater manually on the Core host:

sudo /opt/linknesis/bin/linknesis-updater

The updater reads the update channel from /data/.update-channel (written by the Core), falling back to UPDATE_CHANNEL in /opt/linknesis/.env, and finally to stable. It performs the same safe pull, recreate, and health-check sequence as the timer.

Rollback

If the new container does not become healthy, the updater automatically restores the backup .env file and recreates the container with the previous image tag. Manual rollback is also possible by editing /opt/linknesis/.env, setting CORE_IMAGE_TAG to the previous version, and running:

cd /opt/linknesis
sudo docker compose pull core
sudo docker compose up -d

Troubleshooting

  • Update never starts: verify Core Update is enabled in Settings and that the Core can reach https://linknesis.com/core-versions-<channel>.json.
  • Image pull fails: check registry credentials, internet access, and docker logs -f linknesis-core.
  • Core does not become healthy: inspect docker logs -f linknesis-core; the updater will roll back after the health-check timeout.

© Linknesis. Documentation for the Linknesis network monitoring platform.