Newb questions about updates

Custom Deployment
1

I have the openremote up and run on my own server from. 4 docker containers.

I would like to update to latest version. But…

  1. I don’t know what version I have now. How would I check that?
  2. Once I know. How do I upgrade to the latest version?
2

The manager Docker images have a git-commit label that can be used for figuring out what code was used to build it:

$ docker inspect openremote/manager | grep git-commit
                "git-commit": "1b51518fe1f49a6a605d1bcfda86c0f29ebfe237",

This Git commit hash can be used to find the code in GitHub:

https://github.com/openremote/openremote/commit/1b51518fe1f49a6a605d1bcfda86c0f29ebfe237

The first 7 characters of the hash for each release is also shown on the Releases page on GitHub.

Since the introduction of versioning in OpenRemote you can also specify the manager tag in your Docker Compose file, e.g. openremote/manager:1.3.3 (instead of using the latest tag)

To upgrade to a new version first check the release notes on the Releases page. Then update the tag of the openremote/manager image in your Docker Compose file and recreate the stack (docker compose up -d).

We also recently added the version to the Appearance page in the UI (#1715) in 1.3.3.

3

ok thank you for the answer.
It seems like I am already running the læatest version 1.3.3.
Commit tag is: 907d3b2e9be3ce3480ffa80471d526dd34808e59

So… guess it updates automatically because the docker compuse file uses

image: openremote/manager:${MANAGER_VERSION:-latest}

So if I do docker compiose up, it will pull the new image and use that.

4

The Git commit used for building your image was made on Sep 11, 2024. So you are running a version before the release management was introduced in v1.2.0 (Dec 18, 2024).

If you use the latest tag, Docker will only upgrade your container to the latest version if you first pull the Docker image (i.e. docker compose pull or docker pull openremote/manager:latest) and then recreate the container in the stack (docker compose up -d).

It’s better to specify the image version using the MANAGER_VERSION environment variable (or .env file) now that versioned manager images are published instead of using the default latest tag. That way you will know what version you are running and it prevents unintended upgrades.