Update to 8.0.24 Official

[Gamertech]

Description

The new Network 8.x branch is Official so updating. There are currently reports that 8.0.7 is incompatible with 3rd party routers and 3rd party DHCP/RADIUS.

Motivation and Context

Allows users to use the new 8.0.7 version.
Closes: #693 #702

How Has This Been Tested?

Hopes and dreams. UI hasn't changed any dependencies so if anything breaks, it'll be on Ubiquiti.

Checklist:

Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

• My code follows the code style of this project. (CI will test it anyway and also needs approval)
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[michaelaguiar]

Using this version now, everything appears to be working so far. Thanks!

[c0ldtech]

Using this version now, everything appears to be working so far. Thanks!

This may seem like a stupid question, but how did you do this? Just using :beta and pointing the PKG URL in env does not work for me, as the webserver throws a nullpointer exception and doesn't start (something with java.time, it seems to be a java version issue.

[chkuendig]

Also works for me.

@c0ldtech using docker-compose, this is what I did:

replaced
image: jacobalberty/unifi:latest with build: https://github.com/Gamertech/unifi-docker.git#be8f766283edad8801033e2f09abcbd4df693fd4 in my docker-compose.yml

ran docker-compose build <containername> and docker-compose up <containername> and that was it

[c0ldtech]

@chkuendig thanks a lot! Successfully used the beta image with JDK_JAVA_OPTIONS=--add-opens=java.base/java.time=ALL-UNNAMED as a workaround, will try your way tomorrow.

[Gamertech]

Just a heads up, this isn't based on beta (any more). The beta branch is ancient, like 5.x and I think misses the directory changes that the newer branches have.

I was intending to sync the old beta branch, but it's since gone to Official so I rebased to master. Only real way to get this PR is to build it yourself like chkuendig's method.

[sliwik]

Hi @chkuendig,
I tried your way with following lines at the beginning of my docker-compose.yaml file:

services:
  unifi:
    build: 'https://github.com/Gamertech/unifi-docker.git#be8f766283edad8801033e2f09abcbd4df693fd4'
    container_name: 'unifi-8.x.x'

When running docker-compose build unifi-8.x.x (my container name), I get the following error: ERROR: No such service: unifi-8.x.x
I tried to run docker-compose build unifi (the service name), I get the following error: Building unifi unable to prepare context: unable to find 'git': exec: "git": executable file not found in $PATH

Can you please guide me? Thank you

[Gamertech]

Pulling from Github, you'd need Git installed on the system.

[Arn0uDz]

Anyone has instructions on how to update to this version using Container Manager on Synology DSM 7.2?

[sliwik]

Pulling from Github, you'd need Git installed on the system.

Thank you @Gamertech. It worked.
Another question for future releases: how do I find the build GIT ID like unifi-docker.git#be8f766283edad8801033e2f09abcbd4df693fd4 for 8.0.7?

[arkste]

Anyone has instructions on how to update to this version using Container Manager on Synology DSM 7.2?

if you want, you can use "nexusforge/unifi-docker" as an image.

since i'm dependent on the image myself and looking at how the 7.5.187 update PR wasnt merged since almost two months, i've decided to fork the repo into its own github organization (because multiple maintainers) and update it to the most recent version 8.0.7 myself.

https://github.com/nexusforge/unifi-docker
https://hub.docker.com/repository/docker/nexusforge/unifi-docker/tags

i did it mainly for myself, but am willing to add more ppl to the organization as maintainers if they're interested.

[PeterFalken]

Anyone has instructions on how to update to this version using Container Manager on Synology DSM 7.2?

if you want, you can use "nexusforge/unifi-docker" as an image.

since i'm dependent on the image myself and looking at how the 7.5.187 update PR wasnt merged since almost two months, i've decided to fork the repo into its own github organization (because multiple maintainers) and update it to the most recent version 8.0.7 myself.

https://github.com/nexusforge/unifi-docker https://hub.docker.com/repository/docker/nexusforge/unifi-docker/tags

i did it mainly for myself, but am willing to add more ppl to the organization as maintainers if they're interested.

@arkste, I can volunteer to be a maintainer if needed.

[c0ldtech]

Pulling from Github, you'd need Git installed on the system.

Thank you @Gamertech. It worked.

Another question for future releases: how do I find the build GIT ID like unifi-docker.git#be8f766283edad8801033e2f09abcbd4df693fd4 for 8.0.7?

That's the commit ID.

That (at the end of the URL) is the latest one for example.

[reinhapa]

@jacobalberty any chance to get that merged?

[waja]

For everybody want to test and don't want to build this on it's own, I created a fork and applied this changes. You can grab it at https://github.com/waja/docker-unifi/pkgs/container/unifi/151917726?tag=8.0.7

[arkste]

For everybody want to test and don't want to build this on it's own, I created a fork and applied this changes. You can grab it at https://github.com/waja/docker-unifi/pkgs/container/unifi/151917726?tag=8.0.7

you could've saved your time and just used the image i mentioned almost 4 days ago:

https://github.com/nexusforge/unifi-docker
https://hub.docker.com/repository/docker/nexusforge/unifi-docker

in the long run its probably better that this kind of image is moved to a company account on github with more than one maintainer.

your image is in your personal account, so it has the same risk of beeing abandoned the moment you're afk.

[waja]

your image is in your personal account, so it has the same risk of beeing abandoned the moment you're afk.

I've no intention yet to maintain this in a long run. Hopefully Jacob is coming back and has the time to keep up this project or add more maintainers. Until then, I'll try to keep things up (for my instances) and look how things turning out.

[dbertheau]

Anyone has instructions on how to update to this version using Container Manager on Synology DSM 7.2?

if you want, you can use "nexusforge/unifi-docker" as an image.

since i'm dependent on the image myself and looking at how the 7.5.187 update PR wasnt merged since almost two months, i've decided to fork the repo into its own github organization (because multiple maintainers) and update it to the most recent version 8.0.7 myself.

https://github.com/nexusforge/unifi-docker https://hub.docker.com/repository/docker/nexusforge/unifi-docker/tags

i did it mainly for myself, but am willing to add more ppl to the organization as maintainers if they're interested.

I use Unifi equipment for my home network. I have an older Synology NAS (RS2212+)...only supports Docker and does not support Container Manager. About 5 years ago I setup a Unifi controller in Docker using jacobalberty's image...did this by following youtube videos. My gateway is a UXG Pro. Six switches and six APs installed within my property...home, shops, etc...

The Unifi equipment and Synology NAS with Docker installed Unifi controller has worked great for the five years. But now with version 8.0.7 not being able to download the latest jacobalberty image within my Docker/Synology system, I'm feeling a little uneasy...and, I'm not sure how to update to the latest version using your image.

I have downloaded your image within Docker, but not sure what to do next to. Is it as simple as:

1. backup current settings
2. turn off the jacobalberty container
3. launch the nexusforge image/container
4. then I hope restore the backed up current settings from step 1)

As you can see, I'm a little bit of a novice. I'm retired now. Software developer out of school...many years ago. Always built my own computers and home networks. So, I know enough to be dangerous.

Any "pointing me" in the right direction would be greatly appreciated.

I've also considered maybe another image i.e., LinuxServer??? One other item...I've read that soon we/I may need to install a separate Mongo DB container... I'll research to understand better what this entails...

Thanks...

[buckaroogeek]

Any "pointing me" in the right direction would be greatly appreciated.

I have a similar set up (USG, APs and switches in house, shop, and barn). Synology DS218+ on the network with Docker hosting Unifi Network (formerly Controller). This Synology supports DSM 7.2 which is now has (including Container Manager which is Synology's revised user interface for Docker). I use docker-compose to manage docker. I have containers for unifi, mongodb, and unifi log per Jacob's web site.

For me the steps to upgrade from 7.x (the latest version) to 8.0.7 were:

1. Use Unifi application to export settings backup, just in case.
2. Edit the compose file to change the unifi container to v8 from v7 (I use the v7 or v8 tag. I used this version: https://hub.docker.com/repository/docker/buckaroogeek/unifi/ which I created). In the compose file 'image: "jacobalberty/unifi:V7" ' changed to 'image: "buckaroogeek/unifi:v8" '.
3. Used docker-compose pull to cache the 8.0.7 locally in docker: sudo docker-compose pull unifi. My compose file names the container 'unifi'.
4. Used 'sudo docker-compose up -d unifi to start the new container. This will also stop the old container.
5. Wait for the new version to boot and stabilize. No issues or problems.
6. After verifying success, I use docker rmi to clean out the old images and save disk space on the synology.

Jacob's upgrade instructions at https://github.com/jacobalberty/unifi-docker#upgrading-unifi-controller are sparse but sufficient for those that use docker run to start unifi.

My compose files are available at https://github.com/buckaroogeek/unifi-pihole-doh-docker. I also run pihole and a DOH client and a local docker registry in the same docker instance. The compose.yml file works on DSM 7.2. The docker-compose.yml file is the older version I used on earlier versions of DSM. Since there are multiple compose files, one needs to tell docker-compose what file to use, e.g. sudo docker-compose -f docker-compose.yml pull unifi.

[stavros-k]

At this point I'd consider this project abandoned.
I hope @jacobalberty is good in his health and its just that have more important stuff to deal with, which is fine.

---

That being said, I can recommend this maintainer/image https://github.com/goofball222/unifi
With few "moving" around of data, it can be a drop-in replacement.

Easier would be to download a backup of your current instance and restore with the above image.

[dbertheau]

Okay, thanks guys...

As this is a fun hobby for me, I'm thinking I may start by getting another, more capable and newer, Synology NAS...my RS2212+ is probably 10 years old.

And then start over with the Unifi Network Application and investigate which is the best maintainer/image to go with. I now understand better that my current setup depended on one person to maintain...more risk than I understood. I also hope Jacob is doing ok...

...thanks again

[seerdekens]

I also hope @jacobalberty is doing well.
It looks like this project is abandoned indeed. It's a shame because the quality testing of the container was unmatched.
At least that's what I've read on numerous places. The latest version here was also my first, since I transitioned from a Ubuntu VM to Docker.

I've chose to go for the one from Linuxserver with separate Mongo-DB. So far so good on mu Synology DS-218+ .
https://docs.linuxserver.io/images/docker-unifi-network-application/

[gunsh0hh]

Anyone has instructions on how to update to this version using Container Manager on Synology DSM 7.2?

if you want, you can use "nexusforge/unifi-docker" as an image.

since i'm dependent on the image myself and looking at how the 7.5.187 update PR wasnt merged since almost two months, i've decided to fork the repo into its own github organization (because multiple maintainers) and update it to the most recent version 8.0.7 myself.

https://github.com/nexusforge/unifi-docker https://hub.docker.com/repository/docker/nexusforge/unifi-docker/tags

i did it mainly for myself, but am willing to add more ppl to the organization as maintainers if they're interested.

Thanks for forking and updating this. The image works great.

[kretzu77]

For DSM 7.2.x with Container manager

1. Make/Save last backup from jacobalberty/unifi
2. Stop+Delete jacobalberty/unifi container + Delete jacobalberty/unifi container image
3. download linuxserver/unifi-controller image (latest)
4. Run and config like here: https://www.youtube.com/watch?v=Jvt665LK_bc (in another folder, of course)+ "Restore setup from backup" on 06:09 yt video
5. Averything works

Thank you @jacobalberty for all your past work on this. Wish you all the best.

[HiddeBeumer]

I also hope @jacobalberty is doing well. It looks like this project is abandoned indeed. It's a shame because the quality testing of the container was unmatched. At least that's what I've read on numerous places. The latest version here was also my first, since I transitioned from a Ubuntu VM to Docker.

I've chose to go for the one from Linuxserver with separate Mongo-DB. So far so good on mu Synology DS-218+ . https://docs.linuxserver.io/images/docker-unifi-network-application/

How do you move from the single image version to the 2 image version with separate Mongo container on a synology? so far the documentation assumes that it's on some unix OS where you do the migration on a command line tool.

[dbertheau]

This youtube helped me install the separate containers:
https://youtu.be/oTqUuCU01gM?si=tBKI4x57ROyfAcID

[jacobalberty]

Yes I am alive, just busy with life stuff, Thank you @Gamertech for the pr, sorry it took so long to merge

[MichiFr]

Thank you Jacob and others, too for this new release!

As mentioned above, can I still use my existing Radius profile pointing to a Synology Radius server?

[XMaarten]

Don't use 8.0.24 when you have WAN2 with a static or PPPoE configuration, it gets removed and it is fixed in 8.0.26:

Fixed an issue where WAN2 configurations were removed after a firmware upgrade when using 8.0.24 with a Static or PPPoE WAN configuration.