17 minutes ago, jumperalex said:

Ah well that's fair haha. I "think" compose is actually pretty easy especially once the docker compose add-in is installed. I've been using it for Immich for a bit now with success.

"So do it yourself" you say.

Well using immich, and knowing how to set it up from scratch were two difference things. As for the other way setting up mongo separate, I think that's the point of using compose. It packages it all in one for management, dependancies, etc etc. Immich actually runs 4 dockers! but it's all managed from a single compose file (okay and an env file).

Anyway, like I said above, I'm not poking or demanding. Was just curious about the art of the possible because "yeah sure that is doable" means I wait. "Yeah naw I tried and it failed" means I really look into a VM or using my spare rpi4.

Yes its possible to do this yourself but not via unraid gui I guess which was the goal. Personally I wont be going that direction but you can of course.

For those following along a potential fix I dont understand is being discussed here:

GitHub

Failed to build 10.1.85 · Issue #34 · 11notes/docker-unifi

https://github.com/11notes/docker-unifi/actions/runs/21976591788

So while Im not promising it will be fixed it seems like there is a chance we will get another 2 years or so out of this docker if that works out.

@jumperalex @fat @wayner @wgstarks @bmartino1

4 hours ago, PeteAsking said:

For those following along a potential fix I dont understand is being discussed here:

GitHub

Failed to build 10.1.85 · Issue #34 · 11notes/docker-unifi

https://github.com/11notes/docker-unifi/actions/runs/21976591788

So while Im not promising it will be fixed it seems like there is a chance we will get another 2 years or so out of this docker if that works out.

@jumperalex @fat @wayner @wgstarks @bmartino1

The reason I stayed out of it and other things there is because of their release of the console OS.

There was a few updates back where they actually moved off of Mongoose 3 to mongo 7. unfi ve 8.1+ relase notes... *(UniFi 8.1+ is required for MongoDB 7 support.)

There's also issues going on in the Debian repository which most of this is built on where Debbie and 12 buster and Debian 13 are breaking away from the old Java jdk and everyone wants to be on Java 21 at the moment.

(debain 13 trix will intall v21 as the loest while alot of apps requrie java 11 or 17 to run...)

This update and issue post here is clearly we're referencing an issue between Mongo's db3 which needs to be Mongo's db7 and the Java executable explanation of needing Java version 25 to run the new network application suite due to features in the jdk JRE.

Well I'm sure it could be worked around fixed and updated. It's not really worth it to me in terms of getting something viable.

By all means a separate Docker instance, another can definitely be built reworked and run as intended.

This is why I public archived the lxc variant well that will still run and be updateable.

And attempts to run the console OS as an lxc completely failed due to how they're trying to run podman and supervisor to control the unify arm stack of UniFi protect and what actually runs behind the unify OS on their physical hardware.

And why I posted the MSP guide for the uniFi console, in which case it'd be better to run a Debian virtual machine and install the os console to maintain all features and availability even for for offline access and configurability of your network without the need of a uniFi router...

Besides, the docker Network application has always been fickle based on ubiquity UniFi and how they want to handle software updates, moves and control of the offline system.

Edited February 25Feb 25 by bmartino1

I just bite the bullet and spun up a debian 13 VM and used a script posted in the unifi forums here, to install the UNIFI OS.

https://community.ui.com/questions/UniFi-OS-Server-Installation-Scripts-or-UniFi-Network-Application-Installation-Scripts-or-UniFi-Eas/ccbc7530-dd61-40a7-82ec-22b17f027776

Restored from a backup and readopted all my unifi devices, it was pretty painless.

19 minutes ago, Cambork said:

I just bite the bullet and spun up a debian 13 VM and used a script posted in the unifi forums here, to install the UNIFI OS.

https://community.ui.com/questions/UniFi-OS-Server-Installation-Scripts-or-UniFi-Network-Application-Installation-Scripts-or-UniFi-Eas/ccbc7530-dd61-40a7-82ec-22b17f027776

Restored from a backup and readopted all my unifi devices, it was pretty painless.

Interesting script but I would use the podman method personally. Unclear why they bare bones mongodb when it can be containerized.

I just moved over to a UCG-Fiber. Created a network backup from the self hosted and then imported the backup to the UCG-Fiber. Then on the Unraid UniFi controller I changed the set inform address to that of the UCG-Fiber and turned off the UniFi docker

All went smooth

Please do not update image to 10.1.85 as this breaks the controller.

Deploying a new controller on 10.1.85 is working but cant seem to restore a backup file to it.

My suggestion is to move to a vm with unifi-os-server at this stage still.

Edited March 2Mar 2 by PeteAsking

I think everyone should just deploy unifi os server to a vm. I just did it. Took like 30 minutes and its more full featured and better than the controller anyway.

1 hour ago, PeteAsking said:

I think everyone should just deploy unifi os server to a vm. I just did it. Took like 30 minutes and its more full featured and better than the controller anyway.

👍 Did you follow some certain instructions for this?

10 minutes ago, Ruato said:

👍 Did you follow some certain instructions for this?

It was pretty basic under debian. I think the only commands were:

sudo apt-get install podman

wget https://fw-download.ubnt.com/data/unifi-os-server/1856-linux-x64-5.0.6-33f4990f-6c68-4e72-9d9c-477496c22450.6-x64

sudo chmod +x 1856-linux-x64-5.0.6-33f4990f-6c68-4e72-9d9c-477496c22450.6-x64

sudo ./1856-linux-x64-5.0.6-33f4990f-6c68-4e72-9d9c-477496c22450.6-x64

Then wait for it to install and then goto https://ip-of-vm:11443 (take a long time to start initially).

Then update the network controller (threre is a section to do this in the web interface)

Make sure docker is turned off so you dont have 2 controllers running at the same time.

Then do a restore under the relevant location (also takes a long time).

Then its up and running and adopts all your devices. I had 2 access points I had to reboot manually to get them to adopt but otherwise all worked.

P

For people who want to continue with the network controller can you raise your hands?

To use the network controller you must take a backup of your current controller on whatever version you are on. Then you must stop that docker/rename/delete/archive it as we will be using the backup file you have.

Deploy a new version (Be very careful to check you are not using the same paths if you opted to keep your docker instead of deleting it as by default it will use the same locations on unraid and settings). EG: Expand "more settings" before clicking deploy and change /mnt/user/appdata/unifi-controller-reborn to a different path eg: /mnt/user/appdata/unifi-controller-rebornNEW

Access web UI and choose restore from backup - use previously downloaded file. (Any issues here with restoring let me know as we fixed this very recently so if you try within the next 4 hours, that fix may not have propogated down to you, but I can manually tell you what to do).

This seems to give you a docker network controller that works.

At this point can I ask who would like to use the network controller over the VM method? Reason I ask is there is an advert on login to move to the new VM version form unifi so its pretty clear they want you to move.

Pete

Edited March 2Mar 2 by PeteAsking

I'd prefer a docker container over a VM as it doesn't use as much system resources.

@home I just have one AP, three SSIDs, two vLANs and i already found the latter UniFiController with an extra MongoDB way overkill for what i need.

On the other hand, with my clients, I have more sophisticated networks, needing all the tweaking and monitoring, where i go straight for Unifi OS and apreciate the possibilies within.

Non the less, there's also got to be a simple way to manage a simple wireless network without having to buy a dedicated hardware controller (quite usefull in certain networks), set up a database or a whole dedicated VM, munching away valuable RAM and CPU.

Or am I mistaken here?

1 hour ago, Atomspion said:

I'd prefer a docker container over a VM as it doesn't use as much system resources.

@home I just have one AP, three SSIDs, two vLANs and i already found the latter UniFiController with an extra MongoDB way overkill for what i need.

On the other hand, with my clients, I have more sophisticated networks, needing all the tweaking and monitoring, where i go straight for Unifi OS and apreciate the possibilies within.

Non the less, there's also got to be a simple way to manage a simple wireless network without having to buy a dedicated hardware controller (quite usefull in certain networks), set up a database or a whole dedicated VM, munching away valuable RAM and CPU.

Or am I mistaken here?

Fair. Give the new network controller a go then. To get onto the latest you need to take a backup of the current one and then deploy the new one to a new path and restore the config.

I just did the update using the backup + reinstall method (it worked today after a manual restart —yesterday it still didn’t). Note: you have to manually change the appdata directory if you want to keep the previous container.

For now I’m going to stick with Docker as well—resource-wise, a whole VM for a single AP???

Edited March 3Mar 3 by subivoodoo

I would also like to stay with the docker container.

It's less ressource intensive than a VM and easy to deploy.

Ok I will fix up the docker container xml and have to stay with it myself then to help support it. I will update the first post today later with various instructions.

Everything updated, so long as everyone takes a backup and then restores to a brand new container for 10.1.85-unraid everyone will be fine. Anyone running the 10-unraid alpha tag will break their deployment and need to restore from a backup. Anyone manually changing tags will be fine so long as they take a backup file and restore to a new docker.

I was prepared to make the change to Unifi OS but I am happy to continue to utilize the network control docker image. After all, I do not need the extra features the Unifi OS provides: https://share.google/aimode/f7uGhX0CjsU26rPJg. So, thank for continuing to provide support for this!

1 hour ago, PeteAsking said:

Everything updated, so long as everyone takes a backup and then restores to a brand new container for 10.1.85-unraid everyone will be fine. Anyone running the 10-unraid alpha tag will break their deployment and need to restore from a backup. Anyone manually changing tags will be fine so long as they take a backup file and restore to a new docker.

One question. I am currently on version 10.0.162. Will my backup file work with version 10.1.185? Or should the new container first be set to the same version as I am currently and updated to the version 10.1.185 only after I have restored from backup?

4 minutes ago, Ruato said:

One question. I am currently on version 10.0.162. Will my backup file work with version 10.1.185? Or should the new container first be set to the same version as I am currently and updated to the version 10.1.185 only after I have restored from backup?

No your backup file will work. You must take a backup on the 10.0.162 docker (or any 9x docker for anyone with a 9x version) and then deploy a brand new docker that is 10.1.85 that has not been upgraded at all in any way. Then restore that file to the 10.1.85 docker. If you are able to ssh into the unraid box you could stop your old container, mv the folder to an archive location, then delete your orphaned docker and deploy a new one running 10.1.85 and do the restore. WIth a copy of the old files archived somewhere you can potentially go back if you wanted.

Edited March 3Mar 3 by PeteAsking

On 3/2/2026 at 10:55 AM, PeteAsking said:

Please do not update image to 10.1.85 as this breaks the controller.

Deploying a new controller on 10.1.85 is working but cant seem to restore a backup file to it.

My suggestion is to move to a vm with unifi-os-server at this stage still.

Just FYI for others, I was dumb/brave and had my image tag set to 10-unraid so mine auto-upgraded from 10.0.162 to 10.1.185 and was broken as I have since learned would be expected. I am sharing though because I wanted to let others know I was able to just change my image tag to 10.0.162-unraid and that fixed it so I was able to to then export a recent backup. I was then able to delete and re-get the image from community apps and restore that backup on 10.1.185-unraid tag.

20 hours ago, PeteAsking said:

At this point can I ask who would like to use the network controller over the VM method?

I understand why you would want to end support for this eventually as unifi is obviously soon as well, but as long as you want to keep it up I will continue using it. I don't have a preference between controller vs OS and have changed my system at work over to OS, but for personal use I do prefer containers over VMs simply because they are easier to deploy, auto update, more secure, etc.

Starting with 10.1.85 following message comes up after each login.

Is possible to permanently disable that message?

44 minutes ago, rgreen83 said:

I understand why you would want to end support for this eventually as unifi is obviously soon as well, but as long as you want to keep it up I will continue using it. I don't have a preference between controller vs OS and have changed my system at work over to OS, but for personal use I do prefer containers over VMs simply because they are easier to deploy, auto update, more secure, etc.

Unifi will eventually drop support. Nothing anyone will be able to do to stop that.

34 minutes ago, Taramu said:

Starting with 10.1.85 following message comes up after each login.

Is possible to permanently disable that message?

No they want you to start using it so will be nagging incessantly from now on.

A working docker container for Unifi OS Server seems to exist already:
https://github.com/lemker/unifi-os-server

Would be nice to get your view on it Pete, might this be a good base for an upcoming project with Unraid support?