Upgrading Services

Standard Upgrade Process

1. Review release notes for each service being upgraded
2. Pull new images
3. Restart containers

cd docker
docker compose pull
docker compose up -d --remove-orphans

LiveKit Server

Check the LiveKit changelog before upgrading. LiveKit uses semantic versioning — minor versions are typically backward compatible, major versions may require config changes.

Update the image tag in docker-compose.yml:

livekit:
  image: livekit/livekit-server:v1.8.0   # bump here

LiveKit Egress

Egress and LiveKit Server versions should be kept in sync (same minor version). Check Egress releases.

RTCstack API

The API container is built from source. After pulling new code:

docker compose build api
docker compose up -d api

Redis

Redis 7.x is stable. Before major upgrades, create a backup:

docker compose exec redis redis-cli BGSAVE
docker compose cp redis:/data/dump.rdb ./redis-backup.rdb

MinIO

MinIO upgrades are generally safe. For major version jumps, follow MinIO upgrade guide to handle any format migrations.

Rollback

If an upgrade causes issues, roll back by specifying the previous image tag:

# In docker-compose.yml, revert the image tag
docker compose up -d --remove-orphans

All persistent data (recordings, Redis state) lives in named volumes and is unaffected by image upgrades.