Introduction

Generally, the upgrade process is designed so that upgrading from v9.1 to v9.2 (without following this guidance) will allow your installation to continue to operate with minimal disruption.

However, we recommend reviewing the following information as there are several changes in v9.1 that may cause changes in behaviour, or for you to be unable to use the new functionality.

Only upgrades from v9.0 are supported!

Older pre-release versions can not be upgraded to v9.2, as the configuration file format has changed and is incompatible. Users with early pre-v9.0 release versions must remove and reinstall to continue.

Upgrade considerations

If you are upgrading from v9.0 to v9.2, you must review the existing v9.1 upgrade considerations, as they will apply to your upgrade as well as the list below. You can proceed with the following steps, and the upgrade will happen in one step.

For users upgrading from v9.1 to v9.2:

File ownership and running as non-root
A big change in v9.2 is that the container now runs as a non-root user. For most users, this is a seamless upgrade however, please refer to the special upgrade instructions if any of this applies to your container:
- You have configured an EV_GID setting to use a custom group
- You are using oother Docker optoins in your compose file to change the user/group IDs.
- You use a mounted filesystem for saving recordings to
ONVIF Profile S/T triggers

If you used the events_enabled environment variable in v9.1, this has been deprecated and replaced by event_settings_mode.

If you do nothing the default setting for event_settings_mode will take over, which changes behaviour to save bandwidth/resources and only send alerts if there is a corresponding CAMS alarm rule that uses it.

More info: Configuring an ONVIF camera
Licensing mode
By default, your container will use One-In-One-Out licences (which replace the previous Container licences in CLS). This should result in no change to your encoder.

If you wish to use Four-In-One-Out licences, then you will need to use the EV_LICENSE_TYPE environment variable.

How do I upgrade?

Your upgrade steps will depend on how you installed your container originally

For Docker-style installations

Open up a terminal window, and enter the following:

mkdir evvr
cd evvr

nano compose.yml

You will need to update your compose file with the following changes at the top of the v9.1 file:

services:
    edgevis-encoder:
        image: digitalbarriers/evvr:9.1-latest
        devices:
             - /dev/dri:/dev/dri
        container_name: edgevis-encoder
...

to:

services:
    edgevis-encoder:
        image: digitalbarriers/evvr:9.2-latest
        devices:
             - /dev/dri:/dev/dri
        container_name: edgevis-encoder
...

Change line three to update the version to use 9.2.

To save this file, hit CTRL + O (letter O), then hit Enter to confirm the filename.

To exit nano, hit CTRL + X.

Once you have saved your changes, the following command (executed from your compose file's folder) will update your container to the latest version:

sudo docker compose down
sudo docker compose pull
sudo docker compose up -d

Using Raspberry PiOs?

The syntax for the Docker commands is slightly different! When you see a
"docker compose" command listed, you must add a dash - commands become "docker-compose".

Unless you encounter any errors, your instance of EVVR Container is now running and will continue to run automatically after any machine reboot.

For Debian installations

For most users, simply follow the standard installation instructions.

The installation.DEB file will automatically upgrade your existing installation

If you have hand-edited your compose file, the upgrade will not overwrite your changes.

For Cradlepoint R1900 & E300 installations

Simply follow the standard installation instructions, which will update your image with no loss of recordings/configuration.

For Semtech/Sierra Wireless AirLink XR60 installations

Log in to your router and navigate to Apps > General Status
Download the updated container image from the Registry
- Navigate to the Images section of the page.
- Click the Click Pull Image From A Registry button.
- For Image Reference enter: digitalbarriers/evvr:9.2-latest-lite-arm64
- Ensure Registry Configuration has DocketHub-Public selected
- Click CREATE, then click Save in the orange pop-up.
- The image will now be downloaded from DockerHub - depending on the speed of your internet connection, this can take a few minutes.
- Please wait until the Status column reports Ready before continuing.
Under Container Status, identify your EVVR Container, and hit the STOP button.
At the end of the row hit the [ ... ] button, then select Edit - there are two settings to change:
- Hover over IMAGE, and then select the [ X ] button on the right. This will delete the current image name, and in the resultant pop-up, select the new v9.2.0-lite image.
- If not already, set the RAM LIMIT to 1.2GB.
Add a new entry of /usr/bin/ipseries under the COMMAND section:
Click UPDATE, then click Save in the orange pop-up.
Click the START button, which should start the container back up using the new image.
Once you have confirmed your new image is working successfully, you can remove the old v9.1 image in the IMAGES section to free up space on your device.

Upgrading your container from v9.1 to v9.2