Introduction

Generally, the upgrade process is designed so that upgrading from v9.0 to v9.1 (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.

Upgrade considerations

H.264 hardware acceleration

By default, hardware acceleration is enabled automatically for new Docker installations or new/upgraded Debian upgrades.

Docker upgrades: you will need to add extra lines to your compose file - see example below. Once added, hardware acceleration will be used automatically.

If you do not want to use hardware acceleration, please review the article on how to disable this behaviour using the web interface or environment variables.
Pre-configuration of your container's cameras

There are extra options available to handle the audio configuration of your cameras. The current behaviour won't change, but you can now enable audio automatically on your camera when cameras are added.

If you use environment variables or a seed file to deploy containers, you should review the reference documentation for potential updates.
Pre-configuration of Local Viewer configuration settings

If you have used environment variables to setup local viewing in v9.0, you must review the new changes that allow you to separately enable/disable local viewing and setup the local viewing password. If you don't you may find local viewing disabled after upgrading.
Custom permissions of files stored outside of containers

By default, all files written to the configuration or recording volumes in v9.0 are saved as root/root.

This release will change the group to 5001, while keeping the files written as root. This is to allow users outside the container to read the files, without requiring the use of the root account (by adding their user). Upon upgrade, the container will convert all existing files to use the new group. It is also possible to change the group used to something other than 5001.

The future v9.2 release will allow the user to be set as well. This is to allow the container to run as a non-root user, which will improve security.

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.0 file:

services:
    edgevis-encoder:
        image: digitalbarriers/evvr:9.0.0
        container_name: edgevis-encoder

to:

services:
    edgevis-encoder:
        image: digitalbarriers/evvr:9.1.0
        devices:
             - /dev/dri:/dev/dri
        container_name: edgevis-encoder

There are two changes:

Line 3 - Upgrading the version to use from 9.0 to 9.1
Line 4+5 - Adding the devices: section to pass through your GPU if present

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.1.0-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.1.0-lite image.
- If not already, set the RAM LIMIT to 1.2GB.
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.0 image in the IMAGES section to free up space on your device.

Upgrading your container from v9.0 to v9.1