Upgrading Unifi in Synology Docker


The blog where I copied the command has the above title. Interesting. It is interesting for me because I always have this issue. I need to start writing down everything I did so then I don’t have to reinvent the wheel when I need it again in the future. Just like this one — to upgrade Unifi version in Synology docker.

Luckily, I found this pretty quick.

Create a backup using the Web UI of UniFi by going to Settings > System > Backup and hit Download (Settings only). Once done, it’s time to power off your container:

Docker > Container > [your-unifi-container] > switch it off

Once powered down, proceed to fetch the :latest version of the image:

Docker > Registry > jacobalberty/unifi (:latest)

Hit Download at the top (or Right-click on the image name and select Download this image“
Wait for the download to complete – you should see a notification once that’s done.

Finally, we’re going to reset the container itself:

Docker > Container > [your-unifi-controller] > Action > Reset > Yes

Do The Work

There are lots of productivity advice out there. Various self-help books are becoming very famous. I know there are many people who believe that they are completely useless. That they are selling dreams and empty promises.

I don’t agree. At least, not completely. I agree, though, there are useless books out there. However, I believe that the reason those books are “useless” because people just read them and do nothing about it. While ultimately, the authors of those books, often tell you to do something. To work on it. To work for your success.

Do the work. Even though you are tired. Give it 100%. Be flexible. Is it not the way you accustomed to? Then be flexible, do the work, make it work.

An important ingredient for doing the work is boredom.

And nowadays, being bored seems to be avoided.

If boredom is a necessary ingredient, then portable internet is a disaster for doing the work.

This guy explained it very well – we would do everything to not actually do the work – while doing the work is the ultimate way to go forward. The best productivity advice, indeed.

Upgrading DSM 6 to DSM 7


Synology has released the latest and greatest version of DSM 7 on June 2021 but I just upgraded today. If it ain’t broke, don’t fix it. However, the Christmas holiday give me some room in case the upgrade didn’t go well. Luckily, there is no major issues.

Before Upgrade

I used the following applications before the upgrade:

  • Photo Station
  • Docker — I have my Unifi controller and Folding@home running in containers
  • CardDav Server
  • Video Station

The Upgrade

The upgrade was from DSM 6.x to DSM 7.1.1-42962 Update 3. It is running on DS218+.

Applications That Don’t Work Anymore

Photo Station and CardDav server.

Synology introduced Synology Photos to replace Photo Station. The photos are still there but I needed to install the Synology Photos Mobile on my phone and setting up the automatic backup again. All the photos and videos are still there.

CardDav, however, is a different story. It is replaced by Synology Contacts but all the contacts that I had before were all deleted. Since I am not using CardDav as my main contacts, I have no issues with it. But if you do use carddav heavily, please consider to do the backup before doing the upgrade.

I do remember vividly that they told you about this possibility when I started the upgrade process but I completely ignored it since I am not using CardDav that much.

Applications That Work

There were no issues whatsoever with Docker and the Video Station. They just keep working as expected. All containers are running immediately after the upgrade without problems.

Dependency CCS failed to install

This error has been bugging me last time when I was installing Watson Studio on IBM Cloud Pak for Data, running on OCP 4.8.

Dependency CCS failed to install
Unable to install CSS prerequisite

Apparently the reason is that one of the required service, IBM Common Core Service has not been installed correctly. One of the pods failed to pull the image due to pull secret issue with IBM Entitlement Key.

Please make sure that the secret has been propagated correctly to all worker nodes.

Somehow once it fails, it will be problematic.