> ## Documentation Index
> Fetch the complete documentation index at: https://docs.varios-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Update from 2026.10 to 2026.11

> Step-by-step guide for updating an on-premise installation from 2026.10.x to 2026.11 with versioned Presidio images

This guide walks you through updating an on-premise installation from 2026.10.x to 2026.11. Starting with 2026.11, the DLP services `presidio-analyzer` and `presidio-anonymizer` ship with the product version, which requires you to change their image names in `docker-compose.yml` by hand.

`<TARGETVERSION>` stands for `2026.11` or a later patch release `2026.11.x` provided by the VARIOS AI team. The examples use `/docker/variosai` as the installation directory.

> [!NOTE]
>
> If your installation still runs 2026.08.x, first complete the [update from 2026.08 to 2026.10](https://docs.varios-ai.com/en/monthly/operations/update-2026-08-to-2026-10.md). A direct update from 2026.08 to 2026.11 is not supported.

## A. Beforehand (before the maintenance window)

1. Have the VARIOS AI team confirm that `<TARGETVERSION>` has been released.
2. Check the version and disk space:
   ```bash theme={null}
   cd /docker/variosai
   grep ^VERSION= .env           # 2026.10.x
   df -h /var/lib/docker         # >= 8 GB free
   ```
3. Check the login to the container registry. The update service `varios-update.service` runs as `root` and uses the login stored for `root`, so check it with `sudo`. If you also run `docker` as your own user without `sudo`, check it without `sudo` as well:
   ```bash theme={null}
   sudo docker login registry.varios-ai.com
   ```
4. Check which changes your `docker-compose.yml` needs:
   ```bash theme={null}
   grep -n 'presidio' docker-compose.yml
   grep -c 'STACKNAME' docker-compose.yml
   ```
   If the count for `STACKNAME` is greater than 0, also carry out step 2 in section C.

## B. Backup

Take a snapshot of the virtual machine. Only continue afterwards. See [Backup and Restore](https://docs.varios-ai.com/en/monthly/operations/backup.md) for more information.

```bash theme={null}
cp -a .env .env.bak-$(date +%F)
cp -a docker-compose.yml docker-compose.yml.bak-$(date +%F)
```

## C. Adjust `docker-compose.yml`

`.env` stays unchanged. Do **not** change `VERSION=`.

**1. Switch the Presidio images:** The following command points both DLP services to the versioned images.

```bash theme={null}
sed -i -E \
  -e 's#image: registry\.varios-ai\.com/(avency/|variosai/)?presidio-analyzer:.*#image: registry.varios-ai.com/variosai/presidio-analyzer:${VERSION}#' \
  -e 's#image: registry\.varios-ai\.com/(avency/|variosai/)?presidio-anonymizer:.*#image: registry.varios-ai.com/variosai/presidio-anonymizer:${VERSION}#' \
  docker-compose.yml
grep -n 'presidio' docker-compose.yml
```

Afterwards, the two services read:

```yaml theme={null}
  presidio-analyzer:
    image: registry.varios-ai.com/variosai/presidio-analyzer:${VERSION}
    restart: always
    networks:
      - internal

  presidio-anonymizer:
    image: registry.varios-ai.com/variosai/presidio-anonymizer:${VERSION}
    restart: always
    networks:
      - internal
```

**2. Only if `STACKNAME` occurs:** The following command gives the Traefik routers the fixed name `variosai`.

```bash theme={null}
sed -i 's/\${STACKNAME}/variosai/g' docker-compose.yml
grep -n 'traefik.http' docker-compose.yml
```

If your own files under `traefik/dynamic/` refer to a router or service name, update them as well.

> [!WARNING]
>
> After these changes, do not run `docker compose up -d` or `docker compose pull` until the update in section D. The Presidio images only exist from 2026.11 onwards; with version 2026.10.x still set, the start fails with `manifest unknown`.

Check the file:

```bash theme={null}
docker compose config --quiet && echo OK
docker compose config | grep -E 'image: .*presidio'   # both with variosai/presidio-…
```

## D. Run the update

Choose one of the two options. [systemd Service](https://docs.varios-ai.com/en/monthly/security/systemd-service.md) describes how the update service works.

> [tab] update\_version file
>
> 1. ```bash theme={null}
>    systemctl is-active varios-update.service     # active
>    ```
> 2. ```bash theme={null}
>    echo "<TARGETVERSION>" > update_version
>    ```
> 3. Follow the progress until `Update successfully completed`:
>    ```bash theme={null}
>    journalctl -u varios-update.service -f
>    ```

> [tab] Manual
>
> ```bash theme={null}
> sudo systemctl stop varios-update.service
> sed -i "s/^VERSION=.*/VERSION=<TARGETVERSION>/" .env
> echo "<TARGETVERSION>" > update_version
> docker compose pull
> docker compose up -d
> docker compose ps
> docker compose exec php ./update.sh
> docker system prune -f -a --volumes
> sudo systemctl start varios-update.service
> ```

## E. Verify

1. ```bash theme={null}
   docker compose ps                                              # all running, presidio-analyzer and presidio-anonymizer healthy
   docker compose images | grep -E 'php|presidio|code-interpreter'   # all <TARGETVERSION>
   docker compose exec php curl -s http://presidio-analyzer:3000/health
   ```
2. In the user interface, **System information** shows `<TARGETVERSION>`, and **Service Status** has no red entries.
3. In a chat with DLP active, send a text containing a name and an IBAN, for example "Max Mustermann, IBAN DE89 3704 0044 0532 0130 00". Both findings are detected.
4. Upload a PDF containing personal data. The DLP check completes and shows the findings.
5. Ask an assistant with files a question that can only be answered from its files.
6. ```bash theme={null}
   systemctl is-active varios-update.service     # active
   ```

> [!NOTE]
>
> Starting with 2026.11, VARIOS AI passes attached files and assistant files to the model in full as long as they fit its context window. This can increase token usage. You set the share and the upper limit in the [expert settings](https://docs.varios-ai.com/en/monthly/admin/settings/expert-settings.md) under **File contents in the context**.

## F. If something fails

| Message / symptom | Action |
| - | - |
| `docker compose pull` reports `manifest unknown` for `presidio-analyzer` or `presidio-anonymizer` | Repeat section C, step 1; both images must point to `registry.varios-ai.com/variosai/presidio-…:${VERSION}` |
| `docker compose pull` reports `unauthorized` or `denied` | Run `sudo docker login registry.varios-ai.com`; if you run `docker` without `sudo`, also run `docker login registry.varios-ai.com` |
| `presidio-analyzer` stays `starting` or `unhealthy` | Check `docker compose logs presidio-analyzer`; loading the language models takes a few seconds after start |
| VARIOS AI is no longer reachable via HTTPS, or HTTP no longer redirects | Compare the Traefik labels of the `php` service with the backup from section B (section C, step 2), check `docker compose logs traefik` |
| **Change version** reports "This version cannot be installed yet" | Intended: the update to 2026.11 is blocked in the user interface so that section C is not skipped. Run it as described in section D. If 2026.08.x is still running, first complete the [update from 2026.08 to 2026.10](https://docs.varios-ai.com/en/monthly/operations/update-2026-08-to-2026-10.md) |
| `update.sh` aborts | Read the message, fix the cause, run `docker compose exec php ./update.sh` again |
| `.env` shows the old `VERSION` again | `VERSION` was changed by hand while the update service was running → section D, option **update\_version file** or **Manual** |

> [!WARNING]
>
> **Rollback:** Restore the VM snapshot. Do not downgrade via **Change version**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.