Pin OnlyOffice documentserver docker image to a specific version #6

New issue

Closed

opened 2026-04-26 08:19:02 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-26 08:19:02 +00:00

Member

The deployment runs onlyoffice/documentserver:latest. A new OnlyOffice release that breaks behavior (config schema, URL layout, JWT shape, ...) silently rolls in on the next container recreation.

Acceptance

docker-compose.yml (or whatever ships the documentserver) pins to a specific version tag — current is 9.3.1 (onlyoffice/documentserver:9.3.1 or the immutable digest).
Bumping the version becomes an explicit, reviewable change.
A short note in the deployment README about how to test before bumping (open one document of each type via the e2e suite).

The deployment runs `onlyoffice/documentserver:latest`. A new OnlyOffice release that breaks behavior (config schema, URL layout, JWT shape, ...) silently rolls in on the next container recreation. ## Acceptance - `docker-compose.yml` (or whatever ships the documentserver) pins to a specific version tag — current is 9.3.1 (`onlyoffice/documentserver:9.3.1` or the immutable digest). - Bumping the version becomes an explicit, reviewable change. - A short note in the deployment README about how to test before bumping (open one document of each type via the e2e suite).