MonYvel

Thanks for your help guys! Creating the path & mongo-init.js file first & then deploying the MongoDB container with added path did the trick! The new Unifi controller is up and running here now. (Restoring from backup was also no issue) Now I hope that having a separate MongoDB container does not complicate things to much & breaks every time an update is installed...

@wgstarks & @bmartino1, Thanks for your detailed answers! So, if I understand correctly: First create the mongo-init.js file in a location of my choosing and fil it whit the correct content as stated in the github page, After this deploy the MongoDB container with the correct path configured & manually adding the file name to the host path parameter? I do not need to set certain access rights? The defaults from Unraid are sufficient? I will try a new deploy on Friday when I have some time, will report back with my findings.

Thanks @bmartino1 & @wgstarks for this detailed info about the Mongo & new unifi container in unraid. Unfortunately I'm not getting the init-mongo.js file to work. Every time I try to deploy mongo with the settings you provided above, it will just create some test database. Not the unifi one. Could you elaborate a bit more about this: "*Unraid by default will go to folders you will need to go to where your init-mongo.js file you make is and type in the path to do a docker 1 for 1 file replacement and run." What do you mean exactly? I know that default a init-mongo.js folder is created, do I just remove this folder & replace it with the .js file? Or do i need do do something else? I think it is in this step that something is going wrong for me... Thanks again!