Skip to main content
This guide walks you through updating an on-premise installation from 2026.08.x to 2026.10. With this update, the local code interpreter and the virtual file system become a permanent part of VARIOS AI, which requires manual additions to .env and docker-compose.yml. Starting with 2026.10, VARIOS AI also pulls its images from the container registry registry.varios-ai.com instead of aibroker.azurecr.io. <TARGETVERSION> stands for 2026.10 or a later patch release 2026.10.x provided by the VARIOS AI team. The examples use /docker/variosai as the installation directory.

A. Beforehand (before the maintenance window)

  1. Have the VARIOS AI team confirm that <TARGETVERSION> has been released.
  2. Check disk space and memory:
  3. Carry the login over to the new container registry. Your existing credentials also work for registry.varios-ai.com. The following command reads the login stored for aibroker.azurecr.io and uses it to log in to registry.varios-ai.com. It requires python3. Run it with sudo -H, because the update service varios-update.service runs as root and uses the login stored for root. If you also run docker as your own user without sudo, run the command a second time without sudo -H:
    The output ends with Login Succeeded. If the command aborts, log in directly with the credentials provided by the VARIOS AI team:
  1. Install runsc following the official guide and register it as a Docker runtime: Installation and Docker Quick Start.
  2. Run the Docker restart described there only during the maintenance window, because it restarts all containers.
  3. Verify the installation:

C. Backup

Create a snapshot of the virtual machine. Only continue once it exists. For more information, see Backup and Restore.

D. Adjust .env

  1. Check the tokens:
  2. If no line or only one line is printed, create both tokens from scratch. The first command removes a single existing line, if present:
  3. If you installed gVisor:
  4. Do not change VERSION=.

E. Adjust docker-compose.yml

Extend the existing docker-compose.yml by hand, for example with Vim (vi docker-compose.yml) or Nano (nano docker-compose.yml). 1. Service php → environment: insert after MARKITDOWN_URL
2. Service php → depends_on: add one line
3. Three new services at the services: level, for example before redis::
4. Section networks: at the end of the file
5. Switch the image names to the new registry: The following command replaces the domain aibroker.azurecr.io with registry.varios-ai.com throughout the file. Older installations also still use the path avency/botapi/, which becomes variosai/.
aibroker.azurecr.io must no longer appear in the output. The code interpreter only starts its sandbox from registry.varios-ai.com/variosai/code-interpreter-sandbox-python. Check the file:

F. Run the update

Choose one of the two options. systemd Service describes how the update service works.
  1. Follow the progress until Update successfully completed:

G. After the update: populate the virtual file system

The output must read No virtual filesystem containers exist yet. without a red error line. Otherwise, fix the error first (section I) and then continue.

H. Verify

  1. In the user interface, System information shows <TARGETVERSION> and Service Status has no red entries.
  2. If you installed gVisor: a sandbox run only takes a few seconds. Start the following command before the test chat. It waits for the next sandbox container and prints its runtime:
  3. Start a test chat with the code interpreter: “Use Python to calculate the first 20 prime numbers and save them as primes.txt.” The file appears in the chat and in the Files panel. With gVisor, the command from step 3 now prints runtime=runsc and exits. If the test chat fails, stop the command with Ctrl+C.
  4. Ask an assistant with files a question whose answer can only come from its files.

I. If something fails

Rollback: Restore the VM snapshot. Do not downgrade via Change version.