Update or Roll Back the Workspaces Container

Update Workspaces by replacing the container image while keeping the same data volume. Back up first. If you must roll back, restore that backup into a fresh volume and start the old image. Do not run old code against migrated data. Version 0.2.0 includes migrations 0027 through 0033. Once that release updates a data volume, an older image whose migration set ends before 0033 will refuse to start on it.

Before you update

Read the release notes and migration impact for the new version.
Record the current image version and source commit from /healthz.
Create and verify a cold backup.
Keep the old image tag and the protected environment file available.

You can skip release versions. Workspaces applies each pending migration in filename order during boot.

Update the container

Pull the new image

docker pull ghcr.io/plannotator/workspaces/workspaces-rooms:0.2.0

Stop and remove the old container

docker stop -t 15 rooms
docker rm rooms

Start the new image on the same volume

docker run -d --name rooms \
  --env-file /secure/path/workspaces.env \
  -v ws-data:/data \
  -p 8790:8790 \
  ghcr.io/plannotator/workspaces/workspaces-rooms:0.2.0

Verify the result

docker logs rooms
curl -s http://127.0.0.1:8790/healthz

Confirm the new version and source commit. Sign in, open a known document and its version history, then make a new edit.

A migration failure stops the process before it serves requests. Read the log for the migration filename, keep the failed volume unchanged, and restore the pre-update backup if you cannot correct the cause.

Roll back

Rolling back restores data from before the update. The restored volume will not contain writes made after that backup.

Stop the new container

docker stop -t 15 rooms
docker rm rooms

Restore into a fresh volume

Follow Restore a cold backup. Do not unpack the archive over the migrated volume.

Start the old image

Mount the $RESTORE_VOLUME created by the restore steps and use the exact release tag tied to the backup. This example rolls back to 0.2.0. Keep the command in the same shell.

docker run -d --name rooms \
  --env-file /secure/path/workspaces.env \
  -v "$RESTORE_VOLUME":/data \
  -p 8790:8790 \
  ghcr.io/plannotator/workspaces/workspaces-rooms:0.2.0

Verify the rollback

Check /healthz, sign in, open known documents and versions, and make a new edit. Keep the migrated volume until you have confirmed the restore.

An old image does not start when the volume contains migrations it does not recognize. This prevents old code from using a newer schema. Reviewed July 22, 2026. Maintained by the Plannotator documentation team.

Start

Accounts and organizations

Sharing and access

Documents and collaboration

Agents and developer access

Plans, billing, and seats

Self-hosting and updates

Security and privacy

Troubleshooting

Before you update

Update the container

Roll back

​Before you update

​Update the container

​Roll back

Before you update

Update the container

Roll back