Updating images
The Orchestrator owns updates of the Studio containers. It sets MSK_DISABLE_DOCKER_UPDATE=true in every workspace, which turns off Studio's own Docker update check. Update from the console instead.
How an update is detected
An update is available for a workspace when its image tag, for example curiosityai/curiosity:latest, now points at a different image than the one its container runs. The Orchestrator compares the image ids on the host.
- Check for updates (on Overview and on Images) pulls every image in use and the default image, then refreshes the comparison. Running containers are left alone. The operation log lists the workspaces that have an update.
- The overview and the workspace list show how many workspaces have an update available.
Update one workspace
On the workspace page, choose Update to the latest image. The Orchestrator pulls the image and re-creates the container. The data volume is never touched.
Update all outdated workspaces
Update all on Overview checks which workspaces are outdated and asks you to confirm. It then re-creates them one at a time in a single operation. Running ones restart, and their data is kept. If some fail, the log says which, the operation ends as failed, and the others stay updated. It is a global administrator action.
curl -X POST -H "Authorization: Bearer $ORC_API_TOKEN" https://example.com/api/admin/check-updates
curl -X POST -H "Authorization: Bearer $ORC_API_TOKEN" https://example.com/api/admin/update-all
Pin an image
A workspace's Image field takes any tag. Set curiosityai/curiosity:<version> to hold a workspace on a version, or change ORC_DEFAULT_IMAGE to choose what new workspaces use. Only the global administrator changes a workspace's image. Console users who own workspaces run the default image.
The Orchestrator itself
Updating the Orchestrator does not touch the workspaces. See Installation and Run it in Docker.