June 15, 201610 yr Does anyone have a process for automatically saving controller backups? Has anyone ever had trouble? On the forums it looks like everyone strongly recommends making a backup before even minor controller updates... but this docker updates automatically. If you stopped it for some reason, it would be automatically updated the next time you start it up. Any thoughts on how to mitigate the damage? I ask because there's lots of people having their entire controller configs wiped in the upgrade from 4.x to 5.x. I can handle that now manually, but I'm a little worried it might happen again in the future.
June 21, 201610 yr Does anyone have a process for automatically saving controller backups? Has anyone ever had trouble? On the forums it looks like everyone strongly recommends making a backup before even minor controller updates... but this docker updates automatically. If you stopped it for some reason, it would be automatically updated the next time you start it up. Any thoughts on how to mitigate the damage? I ask because there's lots of people having their entire controller configs wiped in the upgrade from 4.x to 5.x. I can handle that now manually, but I'm a little worried it might happen again in the future. Settings -> Maintenance-> Backup-> Backup Data Retention Is this what you were looking for?
June 23, 201610 yr Does anyone have a process for automatically saving controller backups? Has anyone ever had trouble? On the forums it looks like everyone strongly recommends making a backup before even minor controller updates... but this docker updates automatically. If you stopped it for some reason, it would be automatically updated the next time you start it up. Any thoughts on how to mitigate the damage? I ask because there's lots of people having their entire controller configs wiped in the upgrade from 4.x to 5.x. I can handle that now manually, but I'm a little worried it might happen again in the future. Settings -> Maintenance-> Backup-> Backup Data Retention Is this what you were looking for? That controls how much data is in the manual backup you create. This is a little different. Say your system is running nicely. Ubiquiti makes an update you didn't notice or didn't know about. You restart your unRaid box, and when it comes online the newest Unifi version is installed automatically, but that update breaks your setup or erases your settings (which has happened with at least one recent firmware release). That's not so easy to recover from, because you needed to backup before you even knew there was an update that was going to be installed. I'll just manually backup frequently, but it is a bit concerning.
June 23, 201610 yr There is one on Google for ToughSwitch. You might be able to use that as a framework for making one that works with UniFi. After all, the settings are just stored in a (I think) JSON file.
June 30, 201610 yr Does anyone have a process for automatically saving controller backups? Has anyone ever had trouble? On the forums it looks like everyone strongly recommends making a backup before even minor controller updates... but this docker updates automatically. If you stopped it for some reason, it would be automatically updated the next time you start it up. Any thoughts on how to mitigate the damage? I ask because there's lots of people having their entire controller configs wiped in the upgrade from 4.x to 5.x. I can handle that now manually, but I'm a little worried it might happen again in the future. Settings -> Maintenance-> Backup-> Backup Data Retention Is this what you were looking for? That controls how much data is in the manual backup you create. This is a little different. Say your system is running nicely. Ubiquiti makes an update you didn't notice or didn't know about. You restart your unRaid box, and when it comes online the newest Unifi version is installed automatically, but that update breaks your setup or erases your settings (which has happened with at least one recent firmware release). That's not so easy to recover from, because you needed to backup before you even knew there was an update that was going to be installed. I'll just manually backup frequently, but it is a bit concerning. the new Beta 5.1.0 has auto backup so it won't be long.
June 30, 201610 yr Any news on the latest updated version testing? pushed new image to the docker hub with 5x version.
June 30, 201610 yr Sorry but I am having issues getting this. I seem stuck on 4.8.18 Restarted and tried force update and I am not pulling the 5.x version. My container broken or am in doing something wrong Sent from my Oneplus One using Tapatalk
June 30, 201610 yr Any news on the latest updated version testing? pushed new image to the docker hub with 5x version. Works great! Thanks.
June 30, 201610 yr All of the linuxserver.io dockers are gone for the community apps? Did I Miss something?
June 30, 201610 yr All of the linuxserver.io dockers are gone for the community apps? Did I Miss something? So they are.... I know that ls.io is reorganizing their repositories right now, and I'm sure the apps will be back available shortly.
June 30, 201610 yr All of the linuxserver.io dockers are gone for the community apps? Did I Miss something? So they are.... I know that ls.io is reorganizing their repositories right now, and I'm sure the apps will be back available shortly. Thanks for the info. I took the other unifi docker and put the ls.io info in and it worked. Thanks for the update!
July 4, 201610 yr Sorry but I am having issues getting this. I seem stuck on 4.8.18 Restarted and tried force update and I am not pulling the 5.x version. My container broken or am in doing something wrong Same thing here, so you're not alone. Maybe the update is failing. I'll comb through my logs in the morning.
July 4, 201610 yr Sorry but I am having issues getting this. I seem stuck on 4.8.18 Restarted and tried force update and I am not pulling the 5.x version. My container broken or am in doing something wrong Same thing here, so you're not alone. Maybe the update is failing. I'll comb through my logs in the morning. Try stopping and starting the docker instead of a restart.
July 4, 201610 yr That was with stop/start. I didn't even realize Restart was an option. Gave that a shot too, no luck with either mechanism. Looked through the logs as well. I can see where the server started up, but nothing out of the ordinary in there.
July 4, 201610 yr That was with stop/start. I didn't even realize Restart was an option. Gave that a shot too, no luck with either mechanism. Looked through the logs as well. I can see where the server started up, but nothing out of the ordinary in there. Can you post the logs of the docker pull and the docker container when it's pulled please.
July 5, 201610 yr That was with stop/start. I didn't even realize Restart was an option. Gave that a shot too, no luck with either mechanism. Looked through the logs as well. I can see where the server started up, but nothing out of the ordinary in there. Can you post the logs of the docker pull and the docker container when it's pulled please. I'm not entirely sure how to do that. I will say that opening the docker item like I was going to edit the container, changing nothing, and then clicking save did seem to get me 5.0.7. So that worked in getting it upgraded.
July 13, 20169 yr Is it possible to reduce the size of the image you're using for the container icon? It's massive.
July 13, 20169 yr Is it possible to reduce the size of the image you're using for the container icon? It's massive. My wife says size is important...... but yeah we can reduce the size. How come you noticed? Not something I ever pay any attention to myself...
July 13, 20169 yr when i clicked on the dockers tab in webui, unifi logo was loading like 1999. no biggie, just seems like 128x128 or 256x256 is more than enough.
July 14, 20169 yr when i clicked on the dockers tab in webui, unifi logo was loading like 1999. no biggie, just seems like 128x128 or 256x256 is more than enough. Done.
July 14, 20169 yr when i clicked on the dockers tab in webui, unifi logo was loading like 1999. no biggie, just seems like 128x128 or 256x256 is more than enough. Done. Thanks! Love the container BTW, 5.0 has convinced me to invest in some USGs Sent from my 6055Y using Tapatalk
July 21, 20169 yr Hi all, This docker app was working fine on 6.1.9, two days ago I moved to RC 2 and the app does no longer work. It starts: _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-add-user: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... [cont-init.d] 30-keygen: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. That all looks OK to me. However, I cannot access the Unifi webpage. As soon as the docker start I get the following log entries in my UNRAID log: Jul 21 13:18:55 Unraid kernel: docker0: port 9(vetheca349d) entered forwarding state Jul 21 13:19:03 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:10 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:10 Unraid kernel: docker0: port 9(vetheca349d) entered forwarding state Jul 21 13:19:16 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:23 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:29 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:36 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:43 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:50 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:56 Unraid shfs/user: shfs_write: write: (22) Invalid argument Can anyone point me in the right direction? Thanks
July 21, 20169 yr Hi all, This docker app was working fine on 6.1.9, two days ago I moved to RC 2 and the app does no longer work. It starts: _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-add-user: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... [cont-init.d] 30-keygen: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. That all looks OK to me. However, I cannot access the Unifi webpage. As soon as the docker start I get the following log entries in my UNRAID log: Jul 21 13:18:55 Unraid kernel: docker0: port 9(vetheca349d) entered forwarding state Jul 21 13:19:03 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:10 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:10 Unraid kernel: docker0: port 9(vetheca349d) entered forwarding state Jul 21 13:19:16 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:23 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:29 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:36 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:43 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:50 Unraid shfs/user: shfs_write: write: (22) Invalid argument Jul 21 13:19:56 Unraid shfs/user: shfs_write: write: (22) Invalid argument Can anyone point me in the right direction? Thanks use /mnt/cache/appdata instead of /mnt/user/appdata
Archived
This topic is now archived and is closed to further replies.