13 minutes ago, PeteAsking said:

@bmartino1It is not clear to me why you have ‘privilege = true’ in your setup. This is not default in the setup. 

 

it to enforcer docker root access to write when starting a new docker. it is not always needed. it more permission setting and controls. Will need to re look at squids info on that option for more info.

 

https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

 

more to grant the docker otehr host access such as network devices or gCards need for other use within the docker

 

unRAID Docker FAQ

Q1. What does the Privileged check-box do?

A1. The Privileged checkbox allows the Docker Container to perform certain privileged activities, these are typically required for additional networking functions, such as creating/editing virtual adapters

Edited November 11, 20232 yr by bmartino1
add data

Interesting. This docker is designed to avoid at all costs using root in any way whatsoever so most likely enabling this (privileged) option is breaking things. The image is built under the assumption root will not be used, its possible enabling this is causing the issues you are seeing and everything should function without that option. 

Edited November 11, 20232 yr by PeteAsking

54 minutes ago, bmartino1 said:

 

Restore stilll breaks and stops docker:

 

lets see if it restored?

Rstore sucessfull:

 

 

The restore is designed to work this way for some reason by unifi. So it doesn’t break, it just works like that. If that’s incorrect then unifi would have to fix how it works. 

Edited November 11, 20232 yr by PeteAsking

23 hours ago, PeteAsking said:

The restore is designed to work this way for some reason by unifi. So it doesn’t break, it just works like that. If that’s incorrect then unifi would have to fix how it works. 

 

I highly appreciate you and your work, as it is hard to maintain and create stable dockers.

 

Having ran the older jar file of this unfi controller, literary xp era v0.6. Coming from other networking deployments with multiple ISP with unifi equipment and deployments.... This also isnt' the first nor will it be the last time for unraid /ubquityi / unifi like dockers to do this weird drop deprecate and resync.

Old example is this old stable docker: https://hub.docker.com/r/jacobalberty/unifi

their last unifi version is 7.1.68 the current unfi version is v 7.5.187

 

Jacobalberty has not updated in quite some time. As such, it considered unmaintained as it's not running the latest version. Depending on ubiquity equipment, running an older version isn't a problem. You risk CVE and other by not staying up-to-date. This is harder when running a web server.

 

I can tell you that a restore should not error out the docker. a Action with the webgui should not have a force close due execution with in the web app. per the last error message, what did the restore due to the config file unifi system.properties to cause the error?

 

While I agree that this is more a unify issues, that fact that we have a java error explaining that a thread exception happened. This may be due to a misconfiguration with the JRE and tells me that there is more to the error than just Unfi issue with the restore process.

 

Having finished my testing for a stable production move. My documentation is on the other forum for support for the deprecated unifi docker for transfer. This docker atm is too unstable for me to continue testing for production use cases.

 

Having did a restore in the old deprecated docker and the new one, I can confirm that the restore doesn't kill the docker. (So what setting or action is that docker doing that allows it to continue to run? The restart process, maybe?)

 

I assume some other docker setting may be need like option stop unless restart or other there may be a setting somewhere passed that is enabled by your default configuration.

 

A side explanation Example similar to me adding a custom hostname option to the docker run. I have seen issues within dockers that now the hostname is changed and the hostname is being called and not able to respond as there is a conflict with a hostname within the docker due to the option set.

 

I can't pinpoint it, but the error is clearing, states it was expected a installation or configuration that is not there. That java error due to default docker protection force close a docker for host data protection.

*Not a Hughes problem, especially if it still completes the desired outcome with is a restore of the unifi system.

 

But that leaves a potential vulnabertiy and question for the future and evolution when unify changes to their next production release.

 

When testing it was at least stable, but if I have to delete my docker appdata do a backup restore for each revision. Sorry. I'm out, that's not stable in my book. I will glady help test to try and assist when able and can. Furthermore, I do hope your maintenance and continuation on this continues.

Unclear what you mean 'by each revision'. To upgrade to a later tag you just change the tag and the database auto upgrades. The restore option is if you are moving from another container.

2 hours ago, PeteAsking said:

Unclear what you mean 'by each revision'. To upgrade to a later tag you just change the tag and the database auto upgrades. The restore option is if you are moving from another container.

 

I agree but that didn't work fore me see above post with web error:

Had to do a fresh delete to get working again. Was unable to do a in-place upgrade.

 

Moving from

11notes/unifi:7.5.187 to 11notes/unifi:7.5.187-unraid

 

16 hours ago, bmartino1 said:

 

I agree but that didn't work fore me see above post with web error:

Had to do a fresh delete to get working again. Was unable to do a in-place upgrade.

 

Moving from

11notes/unifi:7.5.187 to 11notes/unifi:7.5.187-unraid

 

That would not be supported as the images are build in different ways, it would be only from one unraid version to the next.

I also just install (/unifi:7.5.187-unraid) per directions.  All was fine, but I needed to adjust Port: 1900 as it was being used to my Plex docker.  It took a `sudo netstat -pna | grep 900` for me to realize 1901 was already snagged by mosquitto, so 1902 it was!

 

Opened the WebUI, restored the backup, and after a docker-page-refresh, it already showed as stopped, so, restarted it, opened the WebUI and followed the prompts to re-add it to my ui.com site. Not sure how I went to the ui.com site - maybe it was a typo/mis-click on my end - but upon re-visiting my local url site, I logged in as before and everything was there (no adoption needed).

 

Great Job, thank you.

sorry, trying to figure out how this is better than the other docker containers? Very curious to give it a try but I want to understand the difference first? 

 

thank you

 

28 minutes ago, ssjucrono said:

trying to figure out how this is better than the other docker container

It's not being discontinued?

1 hour ago, ssjucrono said:

sorry, trying to figure out how this is better than the other docker containers? Very curious to give it a try but I want to understand the difference first? 

 

thank you

 

Pretty much what @JonathanMsaid. I realise this is not well known, but the linuxserver.io one is being deprecated in its current form and this is being developed as a replacement that is similar to how that one worked. 

To continue with linuxserver.io going forward will require 2 dockers to be configured and maintained and communication between them at all times which is very different to the current single docker solution they provide. 

Edited November 15, 20232 yr by PeteAsking

ok good to know. So this one will be updated going forward and maintained? I'll make the switch!

 

trying out this container now.

 

I am having a conflict with port 1900. Plex is also using that port and I do not see an option in the Plex Template to change it. I changed on the unifi reborn but then it wasn't adopting my unifi devices. So I turned plex off and tried using port 1900 on Unifi Reborn and it is still saying it can't bind to 1900 as plex is using it though it is powered off.

 

 

Edited November 16, 20232 yr by ssjucrono

1 hour ago, ssjucrono said:

trying out this container now.

 

I am having a conflict with port 1900. Plex is also using that port and I do not see an option in the Plex Template to change it. I changed on the unifi reborn but then it wasn't adopting my unifi devices. So I turned plex off and tried using port 1900 on Unifi Reborn and it is still saying it can't bind to 1900 as plex is using it though it is powered off.

 

 

What do you have set for “network type”? Should be bridge.

1 hour ago, wgstarks said:

What do you have set for “network type”? Should be bridge.

yes it is set to bridge. Plex is set to host.

5 hours ago, ssjucrono said:

yes it is set to bridge. Plex is set to host.

Strange. I have exactly the same setup and no conflicts over port 1900.

I am using the official PMS Docker?

 

Here is the Unifi Reborn error 

Edited November 17, 20232 yr by ssjucrono

16 minutes ago, ssjucrono said:

I am using the official PMS Docker?

 

Here is the Unifi Reborn error 

I agree this appears like something is already using this port but if what you are saying is accurate and nothing is because everything else is stopped then its an issue one layer up with unraid itself and not something I can address. I cant say why unraid would claim the ports in use if that is in fact untrue. 

Edited November 17, 20232 yr by PeteAsking

yes you are right it is not Plex. It is something else using port 1900 but I have no idea what or how to figure it out 

 

Found this command and figured out it was my docker container airconnect once I turned that off it worked. and again ports are not listed in that docker template 

Edited November 17, 20232 yr by ssjucrono

now I am wondering how long it takes to adopt my unifi devices? IT just keeps trying over and over? sorry for all the newbie questions. 

21 minutes ago, ssjucrono said:

now I am wondering how long it takes to adopt my unifi devices? IT just keeps trying over and over? sorry for all the newbie questions. 

Mine didn’t need to be adopted after I went through the restore procedure. They were already connected.

hmm I also did the restore and it seemed to work. Maybe I need to start over again. 

 

yeah deleted everything and the appdata folder and restored from backup and still just spinning adopting 

 

 

 

does it matter it has a docker IP in the GUI?

 

Edited November 17, 20232 yr by ssjucrono
more info

39 minutes ago, ssjucrono said:

hmm I also did the restore and it seemed to work. Maybe I need to start over again. 

 

yeah deleted everything and the appdata folder and restored from backup and still just spinning adopting 

 

 

 

does it matter it has a docker IP in the GUI?

 

You should configure the container to use the same IP as before or they wont adopt I dont believe, or you might have to unplug them and reboot them. Its a unifi thing.

Okay I will reboot them. I had the controller on a a different IP than I do now. 

rebooting hard rebooting my switch and AP didn't work. I also tried the custom:br0 with the IP I was using prior and the container doesn't seem to work like that?