Unifi no longer support docker, please move to their server version on a VM instead.

CRITICAL:

This docker requires an AVX capable CPU.

There is NO upgrade path from 9x version to 10x. You MUST take a backup, delete the container/rename/archive etc and then redeploy the container from the app store and RESTORE your backup file.

Do NOT move from 9x to 10x by upgrading the container. Ensure when moving to 10x you use 10.1.89-unraid as the first 10x version. 10x requires an avx capable CPU. If your CPU is older than 15 years, you cannot run this container anymore past 9x. Do not ignore this warning, mongodb will be broken if you attempt an upgrade.

ADVANCED/EXPERIENCED USERS QUICK INFO:

Choose your own adventure tag: https://hub.docker.com/r/11notes/unifi/tags

 

Current recommended Home User tag: 11notes/unifi:10.1.89-unraid

(Updated 09/09/2025 - “stable”)

 

Current Company/Corporate recommended tag: 11notes/unifi:9.5.21-unraid

(Updated 19/06/2025 - “old stable”)

 

Current Critical Infrastructure (no downtime) tag: 11notes/unifi:8.6.9-unraid

(Updated 19/06/2025 - “old old stable”)

 Current ISwearOnAllThatIsGoodAndTrueThatIHaveABackupAndConsentToAlphaTesting tag: 11notes/unifi:10-unraid

(Updated continuously - “alpha”)

NOTE: do not reduce the ram allocated to the docker image below 8GB. This is unsafe.

To upgrade to version 10x from version 9x please see this post on page 32:

NORMAL USERS START HERE:

 

The important information at a glance section:

---------------------------------------------------------------------------------------------------------------------------------------------------------

Development status of community app:

Canary: 31/10/2023 - 04/11/2023 [COMPLETE]

Alpha: 04/11/2023 - 23/11/2023 [COMPLETE]

Beta: 23/11/2023 - 08/01/2024 [COMPLETE]

Delta: 08/01/2024 - 19/10/2024 [COMPLETE]

Stable: 19/10/2024 - 04/02/2025 [COMPLETE - stable achieved]

 

Canary - Dev build only, not public use.

Alpha - Testing only, not suitable for home or production use. Request for community to help to test if able.

Beta - Suitable home use only.

Delta - Suitable home or production use, requires specific steps to be followed to function.

Stable - Suitable all deployments, easy deploy ready.

---------------------------------------------------------------------------------------------------------------------------------------------------------

Docker tags of unifi builds:

Alpha: This ‘latest’ tag is now currently disabled as we are not currently testing and does not exist at this time.  If you abuse this tag and complain things break it will be taken away from you forever and you will ruin it for everyone else and I will direct them to your inbox to complain. This is not a joke. You are helping to test if you use this tag and have a backup to restore from.

 

(home) Stable: 11notes/unifi:10.1.89-unraid

Old Stable: 11notes/unifi:9.5.21-unraid

Old Old Stable: 11notes/unifi:8.6.9-unraid

AlphaTester: 11notes/unifi:10-unraid

 

When a new release is available from unifi, the first 7 days after it is released are reserved for internal testing. No tag will be made available until after 7 days irrespective of how many people complain they really need the new version right now. Deal with it.

 

VERY IMPORTANT NOTE, CRITICAL: In the repository there are 2 types of image. version-unraid and just version. eg: 7.5.187-unraid vs 7.5.187.

the pure version numbers run the docker in 1000:1000 and require special changes to the appdata directory permissions to function. If you use the latest tag, you will need to make these changes.

If however you are a normal non alpha tester, you can use the version-unraid tag which correctly sets the user as 99:100 eg: 7.5.187-unraid

When selecting a new tag to upgrade to, always use the version-unraid tag. These are tested specifically for Unraid. The other tags are for pure docker deployments.

 

Alpha (latest tag, do not use) : This tag is either "latest" or has been released by unifi and reverted back to release candidate due to issues. Do not use except for specific reasons understood by you (do not complain to me when deployment breaks, its on you to fix).

Stable: Latest stable build vetted by community for home use only. Newest features present, that are stable.

Old Stable: Latest stable build in production vetted by community for home or production use.

Old Old stable: Production builds that lag behind to avoid issues. Updated less often and skips low quality builds, has fewest new features by design.

---------------------------------------------------------------------------------------------------------------------------------------------------------

 

Unifi-Controller: Unifi. Unraid. Reborn.

https://github.com/pallebone/UnifiUnraidReborn

The how to section:

 

This docker expects you to use tags to move between builds. When you install the docker you will note that a specific tag has been chosen for you on deployment.

Do not use "latest" tag. Using latest tag means we cannot and will not support or help you on this thread. You are considered the fixer/expert if you use latest.

To choose a desired tag review the tags here: https://hub.docker.com/r/11notes/unifi/tags

 

To install this docker

 

Instructions include moving from a different docker image/community app however these steps can be ignored if not appropriate.

 

1) Login to current running controller web interface and take a backup of 7 days on current controller. You will obtain a backup file such as: network_backup_02.11.2023_08-10_v7.5.187.unf

Make sure old version of unifi controller is the same version you will be migrating to. Unifi is difficult if the versions are different. 

 

2) Stop old Unraid controller/Other controller and turn off autostart/disable from self starting. You can leave this old deployment alone at this point in case you ever need it again.

 

3) Go to apps and install new controller (unifi-controller-reborn). Avoid changing random values you dont understand/cant fix yourself in the template.

 

4) Start container and set to autostart. Restore your backup, it will require you to manually start it again after backup is restored.

Note: When you restore, there is no confirmation the restore completes. After a minute or so  the docker simply stops on unraid (refresh docker page on unraid ui) and the unifi web page just hangs on restoring. You must manually start the docker image again when its stops.

 

The container should now be running normally at this point. If not check steps again and ask for help.

 

To Upgrade this docker - eg: from version 7.5.187-unraid to unifi:8.0.7-unraid

 

To upgrade simply edit the docker, change the tag and then hit apply. Your previous tag will look something like:

11notes/unifi:7.5.187-unraid

you will change it to some later version like:

11notes/unifi:8.0.7-unraid

 

YOU WILL NOT ALTER ANY OTHER SETTING DURING THIS UPGRADE STEP. YOU WILL NOT EDIT NETWORKING, PORTS, OR ANYTHING. DONT DO IT.

 

This will result in the best success rate of the docker upgrading if you do this, and then readopting the devices.

 

---------------------------------------------------------------------------------------------------------------------------------------------------------

 

Notes:

Your networking should be the same if coming from an old controller or devices wont re adopt eg:

”I had my networking on the old container set to br0 and a fixed IP - it wouldn't adopt in the new world until I made that match”

 

KNOWN ISSUES:

1) Clicking on the docker under a brX network implementation and using the "WebUI" button does not work. This will never be fixed. Type the ip you set and port you set into a web browser if you use brX networking (instead of bridge). Use bridge networking if this is a deal breaker for you.

 

2) When restoring a unifi config backup file the docker stops, and does not start again automatically due to some error. You must manually intervene and start it when it stops during the restore process. This is being investigated.

 

Removed install instructions no longer needed:

3) Set directory permissions for new container (can be done after deploying image in step 4, see and read instructions).

To do this prior to deploying the app, use command such as:

 

install -d -m 777 -o 99 -g 100 /mnt/user/appdata/unifi-controller-reborn

 

Commands must be used via ssh or the web terminal (little icon in top right of unraid web interface).

 

If you deploy the image first by following step 4 without doing this, and let it create the docker appdata directory, then you will need to stop the docker then run these commands and start it again afterwards:

 

mkdir /mnt/user/appdata/unifi-controller-reborn

chmod 777 /mnt/user/appdata/unifi-controller-reborn

chown nobody /mnt/user/appdata/unifi-controller-reborn

chgrp users /mnt/user/appdata/unifi-controller-reborn

 

The entire point of this is that if you do a 'ls -l' on the directory with your docker containers you will see the permissions are set as:

drwxrwxrwx 1 nobody users   0 Nov  3 16:41 unifi-controller-reborn/

 

By default if you do not do this, the permissions will be drwxr-xr-x and the docker app will not be able to run and write files to this directory.

Edited May 4May 4 by PeteAsking

Unsupported versions list:

 

8.0.24-unraid (Known regressions, skipped version). 

8.0.28-unraid (Version skipped, did not pass testing).

Edited February 1, 20242 yr by PeteAsking

Sweet! I'll get this set up Monday. 

 

Thanks!

unifi-controller-reborn/
drwxr-xr-x 1 nobody  users              16 Nov  5 14:18
 

appears inconsistent. You need to set the permissions to 777 for it to run correctly at this time. 

Please also tell me what version of the controller the backup was made from. 

@bmartino1 please stop the docker from running and use this command:

 

chmod 777 /mnt/user/appdata/unifi-controller-reborn

 

then post the ls -l again. It is not altering the permissions from your output above. 
 

I believe the tags are correct. 

Also what is actually not working? It appears like you can connect with the app after? @bmartino1

Edited November 5, 20232 yr by PeteAsking

Weird I see that too. i have no problem starting over. mainly use the docker to keep the firmware upto date and to stop spaming pihole unifi dxnaames.

 

I have deleted the folder and starting fresh:

 

root@BMM-Unraid:~# mc

root@BMM-Unraid:/mnt/user/appdata# mkdir /mnt/user/appdata/unifi-controller-reborn
root@BMM-Unraid:/mnt/user/appdata# chmod 777 /mnt/user/appdata/unifi-controller-reborn
root@BMM-Unraid:/mnt/user/appdata# chown nobody /mnt/user/appdata/unifi-controller-reborn
root@BMM-Unraid:/mnt/user/appdata# chgrp users /mnt/user/appdata/unifi-controller-reborn
root@BMM-Unraid:/mnt/user/appdata# ls -l
total 52428800
drwxr-xr-x 1 nobody  users             126 Nov  3 22:59 MakeMKV/
drwxrwxrwx 1 nobody  nogroup            58 Sep  7 02:36 Unraid-PiholeDOHDOT/
drwxrwxr-x 1 nobody  users              66 Oct  1 23:46 binhex-syncthing/
drwxr-xr-x 1     100 console           120 Nov  5 01:31 clamav/
-rw-r--r-- 1 nobody  users     53687091200 Nov  5 15:20 docker-xfs.img
drwxr-xr-x 1 nobody  root              312 Nov  5 00:51 macinabox/
drwxr-xr-x 1     999 users             762 Nov  5 14:22 mongodb/
drwxr-xr-x 1 brandon ssh-allow          82 Sep  7 14:41 nextcloud/
drwxr-xr-x 1 nobody  users              14 Sep 28 00:23 plex/
drwxr-xr-x 1 nobody  users              16 Sep  4 18:12 unifi-controller/
drwxrwxrwx 1 nobody  users               0 Nov  5 15:20 unifi-controller-reborn/
drwxr-xr-x 1 nobody  users              16 Nov  5 14:18 unifi-network-application/
drwxrwxrwx 1 nobody  users              40 Nov  1 14:51 vm_custom_icons/
root@BMM-Unraid:/mnt/user/appdata# 

@bmartino1

 

starting afresh sounds fine. Do a restore and let me know. Dont forget to stop the old unifi docker. 

Edited November 5, 20232 yr by PeteAsking

One other thing. This particular tag had an issue where sometimes you have to restart a device to get it to adopt… unifi issue. If that happens just try powercycling the affected device. Could just be a transient error. 

I run a ASUSTeK COMPUTER INC. ROG STRIX B450-F GAMING II with AMD Ryzen 7 5700G with Radeon Graphics @ 3800 MHz and 32 GB of ram

I mainly run some network security dockers and plex server with unraid.

 

Starting fresh, I make the following extra changes:

 

stoped to old docker that will be depricated after i made a back.

I go to system > setting > Backup > download a backup. I now have a file: network_backup_11.05.2023_01-49-PM_v7.5.187.unf this file contins data such as the newrok wifi names and other networking settings.

 

Now to install your verison of the new docker:

*(I have yet to tie that docker to the phone app. the previous post picture is from the old docker.)

 

I go to the community app page and install this docker.

I change your extra parameter from 8 to 4. And add a mac address and hostname for a networking setup.

 

 

I add 2 variables (may not be needed.) mainly for top and resource checking.

 

 

 

You cannot change the uid and gid of the docker at this time. It is unsupported. 
 

also unclear why you are changing other variables such as privileged and so on.
 

the docker is in alpha state. Changes like this have not been attempted or tested at all. Only a very basic config is working at this time. I would encourage not to change anything beyond what is instructed. 

Edited November 5, 20232 yr by PeteAsking

So now I will configure the unfi docker and go to restore my file the same way I backed it up.

 

last time the restore errored the webpage froze and i got a java error in the docker log. let try with out the uig/guid this time.

 

 

I go to setting > system > Backup > 

 

 

i click restore:

 

 

 

 

get the message in the top right:

 

error in docker log:

 

text  error  warn  system  array  login  

Exception in thread "Thread-9" java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
        at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:168)
        at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1172)
        at com.ubnt.service.C.Ö00000(Unknown Source)
        at com.ubnt.ace.Launcher.Ô00000(Unknown Source)
        at java.base/java.lang.Thread.run(Thread.java:833)
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called

** Press ANY KEY to close this window ** 

@bmartino1 I will fix (or try to) the web ui error - blocked at some point this week. 
 

Once the restore happens is the docker stopped? Can you start it again and it is functional or no?

Edited November 5, 20232 yr by PeteAsking

Normally just takes a minute to restore. 

ok, after refreshing the web page the docker did hault and fail went to stop and got execurtion error clicked doker at the top and saw it is off...

Starting the docker did get me back into my instance with a restroe: will now attempt to readopt or see if the restore grabed my ubiquity devices.

 

the restore failed last time and would not go to the web ui. that is when i DM you.

 

Interesting @bmartino1 - so what is working and what is not working at this time?

At this time, everything is working as it should. idk what broke last time. I have tested a hard reset and adopt. that is working. I assumed there was a java error in the docker where something needed to be installed. This is not the case. I will have to play around and see if backup and firmware restores are working. things are good. Thank you again PeteAsking for your assistance on this.

 

 

 

No problem. Thank you for testing this. I will try to work on areas that need improvement. Many thanks for your help. 

side note:

To keep firmware and backups from old system.

 

You will need to restore first. Then copy the firmware and backup folder in its entity. This way you keep downloaded device firmware for your devices. And have a restore point for the future in the even of errors.

 

I also recommend stopping the docker and backing up the entire app data folder for Docker settings and config as a precaution before adding or editing any data.

Small issue, it appears that the support forum link in the docker tab is set incorrectly. It links to the project page rather than this forum thread.

On 11/4/2023 at 2:41 PM, PeteAsking said:

If you deploy the image first by following step 4 without doing this, and let it create the docker appdata directory, then you will need to stop the docker then run these commands and start it again afterwards:

 

mkdir /mnt/user/appdata/unifi-controller-reborn

Another minor issue, if you have already installed the docker then the mkdir command will fail with directory already exists. Only the commands after that are needed.

 

Also, I never got a popup window with the necessary commands to modify the appdata directory. Maybe you have done away with that???

I see that the instructions have been added to the pane in the Apps tab.

 

Overall the install was unevenful because I knew what was required. I think many people won't though and will be posting for help with the install until you can get the initial permissions issue resolved (hopefully).

 

There also seems to be an issue (probably with Unifi) where restores never complete. I noticed the same thing when installing UNA. The page just sits with a notification that the app is restoring. I had to refresh the page and in the case of this docker restart the docker.

4 hours ago, wgstarks said:

Another minor issue, if you have already installed the docker then the mkdir command will fail with directory already exists. Only the commands after that are needed.

 

Also, I never got a popup window with the necessary commands to modify the appdata directory. Maybe you have done away with that???

I see that the instructions have been added to the pane in the Apps tab.

 

Overall the install was unevenful because I knew what was required. I think many people won't though and will be posting for help with the install until you can get the initial permissions issue resolved (hopefully).

 

There also seems to be an issue (probably with Unifi) where restores never complete. I noticed the same thing when installing UNA. The page just sits with a notification that the app is restoring. I had to refresh the page and in the case of this docker restart the docker.

Interesting, thank you. Does clicking on the docker and choosing "webui" work for you now?

 

Also I will try fix the directory permissions but this is a harder problem to resolve.

 

I will update the support forum link

 

10 minutes ago, PeteAsking said:

Does clicking on the docker and choosing "webui" work for you now?

Yes. There is actually a confirmation popup showing that a reboot is required and asking if the user wants to continue the restore process. If you select continue a notification will popup showing a restoring message. It doesn’t seem to ever go away. I waited a few minutes and then refreshed the window. IIRC I got a failed to connect message. Restarting the docker corrected the issue. 
 

I think this is probably a unifi issue. Just posting this in case anyone else has issues with the restore.

20 hours ago, wgstarks said:

Yes. There is actually a confirmation popup showing that a reboot is required and asking if the user wants to continue the restore process. If you select continue a notification will popup showing a restoring message. It doesn’t seem to ever go away. I waited a few minutes and then refreshed the window. IIRC I got a failed to connect message. Restarting the docker corrected the issue. 
 

I think this is probably a unifi issue. Just posting this in case anyone else has issues with the restore.

 

You are correct, when you do a restore, there is no confirmation at all it has restored. You simply see the docker stop on unraid and when it is stopped, then you can start it again, and the restore completed. No other information is presented.