[MSR] Rule do not fire

[MikeReadington]

Hi Everyone,

MSR had a docker image file naming convention change, and I am not exactly sure how to swap the image out. I'm sure it's not rocket science, I've just never done this before.

I am using a Synology NAS, and under the environment tab there is a "REACTOR_IMAGE" variable. Can I just change the image name to the new image naming convention and clear the container, or should I launch a new container and populate the volume location from the previous reactor?

Thanks in advance

[toggledbits]

Unfortunately no, changing the value of the environment variable will not work. You will have to delete the existing container and rebuild it using the newest renamed image. Your configuration and state storage live outside the container, so these will not be disrupted, as long as you specify the same directory in the new container as you did for the old.

[MikeReadington]

Thanks Patrick, sounds easy enough. (I've got backups just in case)

[MikeReadington]

Edited/amended

For anyone not comfortable messing about with Docker inside of a Synology NAS, these are the steps to update to the new image.

Regardless of what you are doing, It is always good idea to have a backup copy of your reactor data folder.

1. Make note of the "Volume" and "Environment" variable for "TZ"
2. Stop and delete old container
3. Delete old image from the "Images"
4. Download the new image
5. Launch new container with new image
6. Under "General Settings" set container to auto start*
7. Under "Volume" populate reactor data folder used in your previous reactor
8. Under "Port Settings" change local port to 8111
9. Under "Environment" hit the plus sign and add variable "TZ" with the value of your timezone.
10. Apply and launch.

That should be it.

As Patrick stated, none of your configuration data is lost since it exists outside of the container.

Thanks again as always Patrick!

*I missed this one because it had been so long since I had setup from scratch. If you forget to do this a restart inside Reactor will cause a shutdown.

[toggledbits]

@mikereadington said in Synology NAS docker image replacement:

Launch new container with new image

Step 2.5 (or earlier) should be "Download the new image". Somebody will forget if you don't say it!

You can also delete the old image (with generic in the name) once the original container is stopped and deleted at step 2.

Also, I found that the GUI left behind some old images that weren't used. You can get rid of unused/partial/remnant images by sshing into your NAS and running

sudo docker image prune -f

[MikeReadington]

@toggledbits

Fair enough