I will let someone else comment on their experiences but the design goals of the project are : 'secure' and 'ease of use'. You are expected to throw whatever resources it needs at it and we expect it has a half decent CPU of 4 cores and 8gb assigned to deploy this docker. In 2025 I expect this requirement to be totally achievable on any modern system.

5 hours ago, NLS said:

Can anybody compare this one with Linuxserver's one?

@NLS I used the Linuxserver UniFi Controller container for years until they decided to require a second, separate container for the database. It seemed less than ideal to maintain two containers in order to run the UniFi Controller.

This container maintains the single container approach and has never presented me any problems at all. It was very easy to migrate from the Linuxserver docker container to this one (when that was supported).

Ubiquiti finally sucked me into the self-contained Controller world with the UniFi Controller built into the router/gateway I use in both my home locations. Since it is required to use the built-in controller, I no longer use this container, although I do keep it installed and updated on my Unraid servers as a backup.

6 hours ago, NLS said:

Can anybody compare this one with Linuxserver's one?

Which is lighter, more maintained, easier to set up?
(tag me if you reply to me please)

@NLS

Some other thoughts.

At one time LSIO members were very active on this forum. I’m not sure that’s still the case. At least all the LSIO members that I knew of have all been mostly absent lately. There is a support thread for the LSIO docker and forum members there willing to offer support but just not necessarily the devs.

Also, new releases on the LSIO container have not been pre-tested. Unifi has a reputation for putting out releases that will brick your container and it can be a major headache to revert to a prior version (in my experience). If you are using the recommended versions of this build they have been tested by at least a few users before being recommended.

So this doesn't need the separate container approach. I trust that I could migrate from the other one by backing up config or something, right?

48 minutes ago, NLS said:

So this doesn't need the separate container approach. I trust that I could migrate from the other one by backing up config or something, right?

We no longer officially support a migration from the old linuxserver option. This was provided for 1 year, and then dropped as 1 year was deemed enough time for users to migrate so there is now no official support.

To do this you can try it on your own, and I would suggest using the oldest tag available in the docker repository and then restore a config from your linuxserver.io deployment. It should work if you do this and dig through the old posts on this page, as people asked many questions during this transition and all managed to do it.

To answer your other question, yes this is a single container approach.

• P

Edited June 20, 20251 yr by PeteAsking

13 hours ago, Hoopster said:

until they decided to require a second, separate container for the database.

They're following Docker best practices, which is to have one container per service. It's not as common with Unraid, but the majority of production deployments of Docker use docker-compose to handle orchestrating apps that need multiple containers.

12 hours ago, Daniel15 said:

They're following Docker best practices, which is to have one container per service. It's not as common with Unraid, but the majority of production deployments of Docker use docker-compose to handle orchestrating apps that need multiple containers.

This depends, on even on that page there are exceptions. We use an ubuntu image that requires an full init system and is designed to be secure, and thus having it all in one is no issue, and arguably more secure (havent checked how linuxserver does their separate containers or what base image they use). I feel the reliability and robustness of the container will over time, speak for itself. As far as I know, once people are up and running they have had near zero issues after. At least based on this forum.

Thanks for this Docker image. It works well and I was able to get up and running with no prior knowledge of any Unifi products. I'm usually a TP-Link Omada user, but the Flex Mini 2.5G is such a good deal (US$49 for a managed five-port 2.5Gbps switch??), and some of their newer wifi access points look like a good replacement for my 2 x EAP670 if I ever want to upgrade those.

1 hour ago, Daniel15 said:

Thanks for this Docker image. It works well and I was able to get up and running with no prior knowledge of any Unifi products. I'm usually a TP-Link Omada user, but the Flex Mini 2.5G is such a good deal (US$49 for a managed five-port 2.5Gbps switch??), and some of their newer wifi access points look like a good replacement for my 2 x EAP670 if I ever want to upgrade those.

The u7 lites are incredible pieces of kit imho and priced fairly for what you get out of them (and seem like they wont ever break). I always get the lites as they have no moving parts and upgrade whenever a new spec comes out like wifi6-wifi7. I have 4 aps around my home so its worth just getting many cheaper but capable aps as I have a large area to cover including the garden area. Works really well.

Edited June 21, 20251 yr by PeteAsking

New Unraid user here - starting out with 7.0.1. I'm not sure if I should tag onto this thread or start a new one for noob questions.

I'm migrating from Unifi Controller 5.9.29 running on a Windows Server.

Yea, that's old, but Ubiquiti went through a rough patch where updates were broken a few years back, so I held with what was working. My APs are UniFi AP-AC-LR running 5.43.

The Windows Server is retiring and I'm moving to my new Unraid server.

I see two Unifi Docker images for Unraid, but only "unifi-controller-reborn" appears to be current and updated.

Is there any tutorial or guidance for migrating an existing network from one controller to another (with minimal downtime)?

I'm new with Docker, and with Docker on Unraid, so any guidance or pre-requisites w.r.t Docker other than enabling it in Unraid?

Can I migrate settings from existing autobackup*.unf files to the new Docker instance?

If Unraid is at a new IP compared to the existing Windows server, how do I migrate the APs to the new Docker on Unraid? I don't see a function to "un-adopt" APs in the existing controller UI.

Should I select the "unifi:8.6.9-unraid" tag since it is the oldest and the smallest step from my existing controller? I like the sound of no downtime. It looks like that is the one offered in the Unraid Apps page: "Repository 11notes/unifi:8.6.9-unraid". Anything else I should do before I click "Install"?

5 minutes ago, timg11 said:

New Unraid user here - starting out with 7.0.1. I'm not sure if I should tag onto this thread or start a new one for noob questions.

I'm migrating from Unifi Controller 5.9.29 running on a Windows Server.

Yea, that's old, but Ubiquiti went through a rough patch where updates were broken a few years back, so I held with what was working. My APs are UniFi AP-AC-LR running 5.43.

The Windows Server is retiring and I'm moving to my new Unraid server.

I see two Unifi Docker images for Unraid, but only "unifi-controller-reborn" appears to be current and updated.

Is there any tutorial or guidance for migrating an existing network from one controller to another (with minimal downtime)?

I'm new with Docker, and with Docker on Unraid, so any guidance or pre-requisites w.r.t Docker other than enabling it in Unraid?

Can I migrate settings from existing autobackup*.unf files to the new Docker instance?

If Unraid is at a new IP compared to the existing Windows server, how do I migrate the APs to the new Docker on Unraid? I don't see a function to "un-adopt" APs in the existing controller UI.

Should I select the "unifi:8.6.9-unraid" tag since it is the oldest and the smallest step from my existing controller? I like the sound of no downtime. It looks like that is the one offered in the Unraid Apps page: "Repository 11notes/unifi:8.6.9-unraid". Anything else I should do before I click "Install"?

I would take a manual backup from your current windows install, then install using this tag fresh: 7.5.187-unraid

Then I would import that backup file and see if it worked. You can then move to an 8 series tag and then 9 so long as the ap’s support it.

Note: if you have very old AP’s unifi dropped support for them. I will try look up what the latest docker image is that supports your ap you mentioned. Try finding this out before you upgrade .

Edited June 21, 20251 yr by PeteAsking

Seems like the ap you listed is supported. Dont forget to set the inform ip or devices wont adopt when you try. And make sure the old network controller is not running at test time.

Thanks!

I created a manual backup with 365 day data retention - 5.9.29-20250621-1619.unf

I'm not sure about your " install using this tag fresh" with link to hub.docker.com.

In the Unraid WebGui Apps page, I find the page for
unifi-controller-reborn with this info:

Application Type	Docker
Categories	Tools:Utilities, Network:Management
Added	Jun 19, 2025
Downloads	More than 10,000
Repository	11notes/unifi:8.6.9-unraid
DockerHub Stars:	15

I was going to just click "Install", thinking that would get it to a ready to run state. Is there any tutorial or guideline for starting with an image on hub.docker.com and getting it running in Unraid?

My oldest AP is 4.0.10.9653, but one of them is 5.43.56.12784 and is working with the current controller fine. So I can upgrade all APs to 5.43.56.12784 before trying the migration.

I saw your second post - Where do I set "the inform ip" Is that in the new controller in the Docker image, or in the old controller?

So I:

1) Bring up new controller in Docker, load backup configuration .unf file

2) Set Inform IP (in old or new controller? presumably old since new doesn't know about APs yet)

3) Shut down old controller

4) Then how to transition APs - will they just find the new controller? or do I need to power cycle each?

9 minutes ago, timg11 said:

Thanks!

I created a manual backup with 365 day data retention - 5.9.29-20250621-1619.unf

I'm not sure about your " install using this tag fresh" with link to hub.docker.com.

In the Unraid WebGui Apps page, I find the page for
unifi-controller-reborn with this info:

Application Type	Docker
Categories	Tools:Utilities, Network:Management
Added	Jun 19, 2025
Downloads	More than 10,000
Repository	11notes/unifi:8.6.9-unraid
DockerHub Stars:	15

I was going to just click "Install", thinking that would get it to a ready to run state. Is there any tutorial or guideline for starting with an image on hub.docker.com and getting it running in Unraid?

My oldest AP is 4.0.10.9653, but one of them is 5.43.56.12784 and is working with the current controller fine. So I can upgrade all APs to 5.43.56.12784 before trying the migration.

I saw your second post - Where do I set "the inform ip" Is that in the new controller in the Docker image, or in the old controller?

So I:

1) Bring up new controller in Docker, load backup configuration .unf file

2) Set Inform IP (in old or new controller? presumably old since new doesn't know about APs yet)

3) Shut down old controller

4) Then how to transition APs - will they just find the new controller? or do I need to power cycle each?

When you hit install it will bring up a page with a newer tag listed. Im saying to change it to an older tag which I suggest above.

Once installed it will be blank. You will need to turn off the old controller, login to this new controller and restore the backup. Then set the inform ip to be the unraid server. Eg: 192.168.2.7 or something.

Hopefully the ap’s will detect the new controller after this has happened. If not reboot the docker on unraid then if still not try one of the ap’s next.

Edited June 21, 20251 yr by PeteAsking

Thanks for quick answers!

On installation, I clicked App install and it took me to Add Container in Unraid GUI.

There I changed the Repository to 11notes/unifi:7.5.187-unraid

I leave network type as Bridge so Unifi will be available at the IP of the Unraid server on port 8443?

Before I click Apply, are there any other settings need to be changed from default other than Repository?

Once installed I will restore the backup configuration.

In the existing controller, There is a setting for "Controller Hostname/IP" which is the IP of the Windows Server. Below that an unchecked option "Override inform host with controller hostname/IP"

So, on the new controller it will need to have the IP of the Unraid server, and I will check the box by "Override inform host with controller hostname/IP" Correct?

There is also the option "Make controller discoverable on L2 network" which is unchecked on the old controller. Should I check it on the new controller? My network is flat L2 on one /24 subnet. There are VLANs for guest networks.

Edited June 21, 20251 yr by timg11

4 minutes ago, timg11 said:

Thanks for quick answers!

On installation, I clicked App install and it took me to Add Container in Unraid GUI.

There I changed the Repository to 11notes/unifi:7.5.187-unraid

I leave network type as Bridge so Unifi will be available at the IP of the Unraid server on port 8443?

Before I click Apply, are there any other settings need to be changed from default other than Repository?

Once installed I will restore the backup configuration.

In the existing controller, There is a setting for "Controller Hostname/IP" which is the IP of the Windows Server. Below that an unchecked option "Override inform host with controller hostname/IP"

So, on the new controller it will need to have the IP of the Unraid server, and I will check the box by "Override inform host with controller hostname/IP" Correct?

There is also the option "Make controller discoverable on L2 network" which is unchecked on the old controller. Should I check it on the new controller? My network is flat L2 on one /24 subnet. There are VLANs for guest networks.

No nothing else to change. Just that tag.

“So, on the new controller it will need to have the IP of the Unraid server, and I will check the box by "Override inform host with controller hostname/IP" Correct?”

Yes if you dont set this then aps will fail to adopt and it wont work.

You dont need the l2 discovery typically. That is mdns and not normally required.

Are the APs with version 4.0.10.9653 supported by 7.5.187, or should I update them to 5.43.56.12784 before moving to the new controller?

Installed the Docker container, and have one warning. Does it matter?

docker run
  -d
  --name='unifi-controller-reborn'
  --net='bridge'
  --pids-limit 2048
  -e TZ="America/Chicago"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="T440"
  -e HOST_CONTAINERNAME="unifi-controller-reborn"
  -e 'MEM_LIMIT'='4096'
  -e 'MEM_STARTUP'='2048'
  -e 'UMASK'='002'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='https://[IP]:[PORT:8443]'
  -l net.unraid.docker.icon='https://user-images.githubusercontent.com/11403137/277435263-1b01facd-1b15-4ba7-9495-e709c291d67f.jpg'
  -p '8443:8443/tcp'
  -p '3478:3478/udp'
  -p '10001:10001/udp'
  -p '8080:8080/tcp'
  -p '1900:1900/udp'
  -p '8843:8843/tcp'
  -p '8880:8880/tcp'
  -p '6789:6789/tcp'
  -p '5514:5514/udp'
  -v '/mnt/user/appdata/unifi-controller-reborn':'/unifi/var':'rw'
  --memory=8G '11notes/unifi:7.5.187-unraid'


WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
66a19e55ad71ac4699f89f5105dad39a742992b5328a572b934da80824ccb7c8

Edited June 21, 20251 yr by timg11

2 minutes ago, timg11 said:

Are the APs with version 4.0.10.9653 supported by 7.5.187, or should I update them to 5.43.56.12784 before moving to the new controller?

Installed the Docker container, and have one warning. Does it matter?

docker run
  -d
  --name='unifi-controller-reborn'
  --net='bridge'
  --pids-limit 2048
  -e TZ="America/Chicago"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="T440"
  -e HOST_CONTAINERNAME="unifi-controller-reborn"
  -e 'MEM_LIMIT'='4096'
  -e 'MEM_STARTUP'='2048'
  -e 'UMASK'='002'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='https://[IP]:[PORT:8443]'
  -l net.unraid.docker.icon='https://user-images.githubusercontent.com/11403137/277435263-1b01facd-1b15-4ba7-9495-e709c291d67f.jpg'
  -p '8443:8443/tcp'
  -p '3478:3478/udp'
  -p '10001:10001/udp'
  -p '8080:8080/tcp'
  -p '1900:1900/udp'
  -p '8843:8843/tcp'
  -p '8880:8880/tcp'
  -p '6789:6789/tcp'
  -p '5514:5514/udp'
  -v '/mnt/user/appdata/unifi-controller-reborn':'/unifi/var':'rw'
  --memory=8G '11notes/unifi:7.5.187-unraid'


WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
66a19e55ad71ac4699f89f5105dad39a742992b5328a572b934da80824ccb7c8

No clue if they are supported. You should look that up, your site specific requirements etc.

The error is normal and unraid related. Dont worry about it.

What happened @timg11 ?

Thanks again for all your help! I'm back again today.

I have the new controller running. I can access the Unifi controller dashboard at the Unraid server IP:

https://192.168.27.4:8443/manage/default/dashboard

On the dashboard, I see this:

Self-HostedNetwork 7.5.187

Server IP 172.17.0.2

Why is that server IP different than the Unraid server? Is that something to do with Docker?

Edit - yes - answered this question. I see that IP under Container IP in the Unraid Docker Container page.

I restored the Unifi backup and the Docker container shut down and did not restart.

I changed Auto-start to On, and restarted it.

I have not set the Override IP and the old controller is still running.

I see the error in the image below.

In the old V5 controller, the the override IP was in Settings / Controller / Controller Settings.

In the new V7.5 controller, the only settings that are not grayed out are Wi-Fi, Networks, Profiles, and System.

Profiles says "a gateway or switch is required". I do not find the controller settings for IP and Override under System.

Edit - Found Inform - there was an Advanced tab hidden behind the warning dialog above. When I closed it, I clicked Advanced, and scrolling down found a checkbox for Inform Host - Override. I'm ready to shut down the old controller and check the box, unless there are settings in the Wi-Fi configuration (warning dialog above) that I should attend to first.

Edited June 22, 20251 yr by timg11

@timg11 it sounds like you are basically done.

Remember I can support installing the docker but how the actual controller works and what it supports - that is up to unifi. If there is some warning or error with your config you can go to their forums and ask them what to do. We dont create the code or the unifi controller and have no say over how it functions.

That error has been raised on their forums as a bug or some sort of anomaly. How to resolve it exactly, you can investigate directly with them: https://community.ui.com/questions/Your-WiFi-networks-need-attention-Your-previous-WLAN-Override-configurations-are-not-supported-by-t/f30cf0fb-f54a-425d-af8f-875e4b8d6b0d

End of the day there will bound to be some fixing up of your config to be done after waiting so long before updating. You are essentially 3 years out of band for updates. Unifi barely support moving between each update properly, so you might want to manage your expectations on expecting everything to go 100% smoothly.

As far as I can tell, barring some functionality issues you are good to go. Engage with their forums if you consider the last few steps to be a big deal or just bite the bullet and go for it and fix anything that needs fixing after.

Good luck

P

@PeteAsking thanks again for all your help!

I've got the AP's migrated to the controller on the new server in the Docker container. I've updated the APs to the latest firmware. Everything seems to be working!

1 minute ago, timg11 said:

@PeteAsking thanks again for all your help!

I've got the AP's migrated to the controller on the new server in the Docker container. I've updated the APs to the latest firmware. Everything seems to be working!

Good job. Take a backup and update the container to old old stable at least and then follow that update path (check the forum 1-2 times a year for an updated old old stable tag).

@PeteAsking Kinda OT but 11notes has been creating quite a few rootless,distroless images. Would you be willing to bring them over to the Unraid Community Apps as you are already doing this one?

as per his reddit/github:

6 minutes ago, RobertCajun said:

@PeteAsking Kinda OT but 11notes has been creating quite a few rootless,distroless images. Would you be willing to bring them over to the Unraid Community Apps as you are already doing this one?

as per his reddit/github:

Unraid is not compatible with this type of image which is why they were never brought over, and they dont work. We tried to get them working but was impossible due to how unraid dockers work.