CHBMB Posted November 22, 2016 Share Posted November 22, 2016 /mnt/disk1/appdata/unifi/ was /mnt/user/appdata/unifi/ OK, should have been fixed in V6.2.4 of unraid. As an aside, you'll get much better performance from your docker containers if you can put the appdata on a cache disk. Link to comment
creon Posted November 22, 2016 Share Posted November 22, 2016 planning to add some drives then i gone add a ssd cache disk for all the dockers Link to comment
CHBMB Posted December 2, 2016 Share Posted December 2, 2016 is 5.3.8 out? When it hits the repos our container will get updated the following Friday. We have no control over when it hits the repo. Link to comment
sparklyballs Posted December 2, 2016 Share Posted December 2, 2016 is 5.3.8 out? No it is not, at the time of writing it is a release candidate and not a full release. https://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-5-3-8-Stable-Candidate-has-been-released/ba-p/1749831 Link to comment
H2O_King89 Posted December 10, 2016 Share Posted December 10, 2016 did it not make it to todays updates? Link to comment
CHBMB Posted December 10, 2016 Share Posted December 10, 2016 did it not make it to todays updates? Bit difficult when they haven't released it into their stable repo yet.... From their statement. "It will be posted to our downloads page and pushed to the repo on 12.12.16." Link to comment
H2O_King89 Posted December 11, 2016 Share Posted December 11, 2016 did it not make it to todays updates? Bit difficult when they haven't released it into their stable repo yet.... From their statement. "It will be posted to our downloads page and pushed to the repo on 12.12.16." ohh thought they said they where pushing it Wed/7 guess have to wait another week. Link to comment
yippy3000 Posted December 14, 2016 Share Posted December 14, 2016 Can you add port 6789 to the default set of ports that the docker uses? This port is used to connect to the controller by the iPhone App for the "WiFi Speed Test" functionality. Link to comment
sparklyballs Posted December 14, 2016 Share Posted December 14, 2016 Can you add port 6789 to the default set of ports that the docker uses? This port is used to connect to the controller by the iPhone App for the "WiFi Speed Test" functionality. you can manually add any port using the edit function, which is preferable to opening another port up for everyone. Link to comment
David Bott Posted December 17, 2016 Share Posted December 17, 2016 Hi All... Any word on the current version? Has the stable repo not been released yet so it can be updated? Thanks Link to comment
CHBMB Posted December 17, 2016 Share Posted December 17, 2016 Hi All... Any word on the current version? Has the stable repo not been released yet so it can be updated? Thanks Dunno, should have been updated last night as part of our weekly update. I know a few days ago there was an issue with the new version so it wouldn't have worked. https://github.com/linuxserver/docker-unifi/issues/14 Easy answer is update and see for yourself. Link to comment
David Bott Posted December 17, 2016 Share Posted December 17, 2016 Doah! Thats not good of them. I have not installed yet. I wanted to install the current version if I was going to install. Link to comment
CHBMB Posted December 17, 2016 Share Posted December 17, 2016 Not a Unifi user myself, just pulled it and it's 5.3.8. Which is the current "must have" version but will undoubtedly become the older "need a newer version" eventually. Link to comment
David Bott Posted December 17, 2016 Share Posted December 17, 2016 Not a Unifi user myself, just pulled it and it's 5.3.8. Which is the current "must have" version but will undoubtedly become the older "need a newer version" eventually. Thats good. The point being, to start at least current. Upgrade will come, but I surely did not want to start from an older version. Thanks for checking. Maybe someone needed to update the version info if it has not been done. Thanks again for your help. Link to comment
CHBMB Posted December 17, 2016 Share Posted December 17, 2016 Not a Unifi user myself, just pulled it and it's 5.3.8. Which is the current "must have" version but will undoubtedly become the older "need a newer version" eventually. Thats good. The point being, to start at least current. Upgrade will come, but I surely did not want to start from an older version. Thanks for checking. Maybe someone needed to update the version info if it has not been done. Thanks again for your help. We've got enough to do without bumping a change log for every version update for every app. Just not feasible. Link to comment
poldim Posted December 18, 2016 Share Posted December 18, 2016 Any idea what could be causing this? Stopping container: unifi Error: Error code Removing container: unifi Error: Error code Stopping container: unifi Error: Error code Removing container: unifi Successfully removed container 'unifi' Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="unifi" --net="bridge" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8330:8080/tcp -p 8081:8081/tcp -p 8443:8443/tcp -p 8843:8843/tcp -p 8880:8880/tcp -v "/mnt/user/appdata/unifi":"/config":rw linuxserver/unifi docker: Error response from daemon: Conflict. The name "/unifi" is already in use by container 81bfbc5d84a4734840ea49e077d35240eec30b29ec246a7e7d1d605e5a0a5f79. You have to remove (or rename) that container to be able to reuse that name.. See '/usr/bin/docker run --help'. The command failed. Link to comment
CHBMB Posted December 18, 2016 Share Posted December 18, 2016 Any idea what could be causing this? Stopping container: unifi The name "/unifi" is already in use by container 81bfbc5d84a4734840ea49e077d35240eec30b29ec246a7e7d1d605e5a0a5f79. You have to remove (or rename) that container to be able to reuse that name.. [/quote] Sounds like something tripped up in the docker service when you tried to upgrade. I'd remove your existing container and then try and re-add it. Link to comment
poldim Posted December 18, 2016 Share Posted December 18, 2016 Sounds like something tripped up in the docker service when you tried to upgrade. I'd remove your existing container and then try and re-add it. I had to reboot unraid as the docker was completely unresponsive. Link to comment
Dephcon Posted December 21, 2016 Share Posted December 21, 2016 Not a Unifi user myself, just pulled it and it's 5.3.8. Which is the current "must have" version but will undoubtedly become the older "need a newer version" eventually. Thanks for the update! Link to comment
marduk201 Posted December 29, 2016 Share Posted December 29, 2016 Hey there man sorry for the bother. i was wondering if happen to be planing to make a docker for unifi voice? love your work. thank you for your time. Link to comment
Stinkpickle Posted December 29, 2016 Share Posted December 29, 2016 Having issues with this docker, I have it running on a 2nd Unraid server fine. Having issues on this server. Docker is started and appears running ok, however I cannot access WebGUI via port 8443. Config: Unifi Log: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/index.php/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: 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. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/index.php/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: 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. Unraid Log: Dec 29 15:08:03 Tech_Server shfs/user: err: shfs_write: write: (22) Invalid argument Dec 29 15:08:07 Tech_Server shfs/user: err: shfs_write: write: (22) Invalid argument Dec 29 15:08:11 Tech_Server shfs/user: err: shfs_write: write: (22) Invalid argument Dec 29 15:08:15 Tech_Server shfs/user: err: shfs_write: write: (22) Invalid argument Any help appreciated, thanks! Link to comment
sparklyballs Posted December 29, 2016 Share Posted December 29, 2016 Having issues with this docker, I have it running on a 2nd Unraid server fine. Having issues on this server. Docker is started and appears running ok, however I cannot access WebGUI via port 8443. Config: Unifi Log: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/index.php/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: 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. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/index.php/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: 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. Unraid Log: Dec 29 15:08:03 Tech_Server shfs/user: err: shfs_write: write: (22) Invalid argument Dec 29 15:08:07 Tech_Server shfs/user: err: shfs_write: write: (22) Invalid argument Dec 29 15:08:11 Tech_Server shfs/user: err: shfs_write: write: (22) Invalid argument Dec 29 15:08:15 Tech_Server shfs/user: err: shfs_write: write: (22) Invalid argument Any help appreciated, thanks! looks to be an unraid problem to me Link to comment
Stinkpickle Posted December 30, 2016 Share Posted December 30, 2016 looks to be an unraid problem to me Yes I agree. I did what user creon did on page 12; "/mnt/disk1/appdata/unifi/ was /mnt/user/appdata/unifi/" and it fixed it. Unraid version 6.2.4 Link to comment
vinnybhaskar Posted December 30, 2016 Share Posted December 30, 2016 use /mnt/cache/appdata instead of /mnt/user/appdata Any specific reasons why this Docker images needs /mnt/cache/appdata instead of /mnt/user/appdata? A lot of other Docker images I use (even from LSIO) works well with /mnt/user/appdata. /mnt/disk1/appdata/unifi/ was /mnt/user/appdata/unifi/ OK, should have been fixed in V6.2.4 of unraid. As an aside, you'll get much better performance from your docker containers if you can put the appdata on a cache disk. I don't see any mention of any fix in unRAID 6.2.4 for the above issue. Could you please explain? Link to comment
Recommended Posts