dirtysanchez

i guess the ports for the devices to be seen are immutable. change the ports on the other dockers where you have a clash. You can change the ports the Docker uses internally by editing the system.properties file in the docker config directory.

Thank you!

Any thoughts on creating a Ubiquiti UniFi controller docker? I know one already exists by pducharme, but he doesn't seem to be around much and the UniFi controller was updated to 4.7.5 almost a month ago and his docker is still at 4.6.6.

It needs to be mapped to the location the Mumble container will store it's data. Same as any other docker (but usually called /config in other dockers). For example /mnt/cache/appdata/mumble.

Er may or may not be working on souch a thing, but consensus in the group is that sonarr is better Yes, I've seen the same mentioned by others as well. I guess I just haven't tried to migrate to Sonarr yet as it's quite a bit more difficult to get setup and working properly (or so I've heard), but once running it puts SickBeard to shame. Maybe I'll bite the bullet this weekend and give it a shot.

Any chance of a linuxserver.io SickBeard Docker? I've migrated all of my Dockers to the linuxserver.io Dockers where possible, but no Docker for SickBeard makes me sad...

I did similar to jumperalex. I remapped /transcode in the Docker config from /tmp to /mnt/cache/apps/plex/Library/Application Support/Plex Media Server/Cache/Transcode. I didn't change the path inside Plex itself as I mapped the full path to the transcode directory to /transcode in the Docker.

hex, you are correct about Plex's behavior and it is why I advocated against moving transcoding to RAM in the past. I had the same problem as dirtysanchez, but it was only on long high bit rate videos (movie BD rips). All other stuff ran fine. When I dug into it I was basically juuuuuust not hitting the wall with the shorter lower bit rate stuff but the BD movie rips, at full bit rate, would fill /tmp in about 30-45 min. Crash. flush. restart. rinse. repeat. Frankly the concern over SSD wear is misplaced given all current evidence and most plex / unraid implementations I can guess at. Even with 24/7 streaming of a reasonable number of 20mbit streams the SSD will outlive most people, no less its likely useful life. Hex, they are approx 1.5GB 720p mkv files. It is palying on a Roku, and so is resulting in only the audio being remuxed, therefore the transcoded file size should be approx 1.5GB. It's certainly filling up /tmp before the play completes. I'm going to have to agree with jumperalex here. While transcoding to RAM can save a bit of wear and tear on the cache drive (assuming SSD) it's likely not something that is going to make a significant difference in the life of the SSD, assuming newer-gen SSD's. They have proven to have significantly longer endurance than even the manufacturer ratings in most cases, and even with the added writes of transcoding to the SSD will likely outlast their useful life. I have moved transcoding back to the SSD and will leave it there. If you can transcode to RAM without issues, then I see no point in not doing so. But if you have issues with /tmp filling up, it's probably best to just move transcoding back to cache and be done with it.

I did. It looks like they are related to the Community Applications plugin. Here's a snip from one of the files { "apps": 230, "requests": 72, "last_updated": "25th September 2015 at 17:42:37", "last_updated_timestamp": "1443199357", "applist": [ { "Beta": "False", "Category": "Network:Voip", "Name": "binhex-teamspeak", "Description": "\n TeamSpeak is proprietary voice-over-Internet Protocol (VoIP) software that allows computer users to speak on a chat channel with fellow computer users, much like a telephone conference call. A TeamSpeak user will often wear a headset with an integrated microphone. Users use the TeamSpeak client software to connect to a TeamSpeak server of their choice, from there they can join chat channels and discuss things.[br][br]\n [b][u][span style='color: #E80000;']Configuration[/span][/u][/b][br]\n [b]/config[/b] This is where teamspeak will store it's configuration file, database and logs.[br][br]\n [b][u][span style='color: #E80000;']Notes[/span][/u][/b][br]\n Connect to the server using the TeamSpeak client with the host IP address and port 9987.[br]\n To authenticate use the privilege key shown in the supervisord.log file in the host mapped /config folder.\n ", "Overview": "\n TeamSpeak is proprietary voice-over-Internet Protocol (VoIP) software that allows computer users to speak on a chat channel with fellow computer users, much like a telephone conference call. A TeamSpeak user will often wear a headset with an integrated microphone. Users use the TeamSpeak client software to connect to a TeamSpeak server of their choice, from there they can join chat channels and discuss things.\n ", "Support": "http://lime-technology.com/forum/index.php?topic=38055.0", "Registry": "https://registry.hub.docker.com/u/binhex/arch-teamspeak/", "GitHub": "https://github.com/binhex/arch-teamspeak", "Repository": "binhex/arch-teamspeak", "BindTime": "true", "Privileged": "false", "Networking": { "Mode": "host", "Publish": "\n " }, "Environment": { "Variable": [ { "Name": "", "Value": "" } ] }, "Data": { "Volume": [ { "HostDir": "path to config", "ContainerDir": "/config", "Mode": "rw"

I have been transcoding to /tmp for quite some time and never had issues. Recently (past 2 weeks or so) I have started getting errors where Plex suddenly stops playing and states the file is unavailable. I have traced this down to /tmp running out of free space. I can watch it edge up to 100% full while a transcode is happening and then the transcode dies. I have looked everything over but nothing makes sense, so I thought I'd post up to see if anyone can offer guidance and/or point out what I'm not seeing. System has 8GB RAM, so as expected /tmp is roughly 4GB root@Landfill:/tmp# df -h /tmp Filesystem Size Used Avail Use% Mounted on - 3.8G 3.5G 290M 93% / But why is /tmp 93% full? It is approx 93% full even after a reboot. SO let's look at what's in /tmp root@Landfill:/tmp# du -h 0 ./mc-root 24K ./community.applications/tempFiles 24K ./community.applications 28K ./notifications/archive 0 ./notifications/unread 28K ./notifications 32K ./plugins 0 ./.X11-unix 0 ./.ICE-unix 32M . root@Landfill:/tmp# ls community.applications/ tmp-1661007850.url tmp-399711444.url mc-root/ tmp-168813488.url tmp-449460109.url notifications/ tmp-1719190793.url tmp-456017590.url plugins/ tmp-1876646817.url tmp-477880073.url tmp-1075403738.url tmp-1892929066.url tmp-505641119.url tmp-1094819657.url tmp-1895527982.url tmp-524278372.url tmp-1100506559.url tmp-1952698197.url tmp-558278473.url tmp-1206292614.url tmp-201109261.url tmp-597112372.url tmp-1248792920.url tmp-2011622529.url tmp-602322518.url tmp-1275068659.url tmp-2067235427.url tmp-656886916.url tmp-1280569778.url tmp-207572655.url tmp-682545064.url tmp-1290055322.url tmp-209482678.url tmp-714381734.url tmp-1350278630.url tmp-21930234.url tmp-770145398.url tmp-1547960682.url tmp-350663172.url tmp-875515522.url tmp-1567121976.url tmp-354557422.url tmp-912727871.url tmp-1622958749.url tmp-384040099.url tmp-924626499.url tmp-1648043674.url tmp-386724013.url tmp-991523516.url root@Landfill:/tmp# So according to du, there's approximately 32M of files in /tmp, but according to df -h there's approximately 3.5G used. There's also a lot of tmp-xxxxxxxxxxxxx.url files. Anyone know what these are (or does it even matter)? I know the issue here is there's something I don't understand about how Linux works. I'm assuming most of the space in /tmp is cached for other reasons? What am I missing? In the mean time I moved transcoding back to the cache drive and it's working fine, but I'd like to keep it in RAM if possible.

Please.

Define "adoption fails outright in the first place"? Unless your DHCP server is handing out the controller address to the AP when it leases an address, which it's not unless you specifically configured it to do so, you have to tell the AP where the controller is. That is done with the set-inform command. Why Ubiquiti made it so that you need to do it twice is beyond me, but it needs to be done once, then adopt in controller, then set-inform needs to be run again before the AP will provision. For the life of me I can't find official UBNT documentation staring so, but here's a website which shows it needing to be done twice. There are also numerous posts in the UBNT forums regarding the issue. http://helpdesk.maytechgroup.com/support/solutions/articles/3000008280-how-to-move-a-ubiquiti-unifi-access-point-to-a-new-controller-v2-x-. As to why your first AP worked without doing so but your 2nd didn't is definitely strange. I only have a single AP but I did have to set-inform twice to get it initially set up.

You actually have to run the set-inform command twice, once before and once after adoption. Doing it the second time is what solved your problem.

I have had plexWatch running for many months now, but all of a sudden the docker will no longer start. I know this is needo's docker, so I'm not sure if you support it, or if it is supported at all. In any case, here is the error from the docker log when you attempt to start the docker. Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: git-man liberror-perl patch rsync Suggested packages: gettext-base git-daemon-run git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-arch git-bzr git-cvs git-mediawiki git-svn ed diffutils-doc The following NEW packages will be installed: git git-man liberror-perl patch rsync 0 upgraded, 5 newly installed, 0 to remove and 77 not upgraded. Need to get 84.3 kB/3713 kB of archives. After this operation, 22.5 MB of additional disk space will be used. Err http://archive.ubuntu.com/ubuntu/ trusty-updates/main patch amd64 2.7.1-4ubuntu2 404 Not Found [iP: 91.189.92.201 80] Any help would be appreciated. EDIT: I found the needo thread, I have posted for support in there. Sorry for the confusion.

Have never used nor had the need for them, but can see how they are beneficial in certain situations.

Yes, I've heard nothing but good things about the EdgeMax router. Thank you for mentioning that the EdgeMax router is a prosumer product, as anyone considering purchasing one needs to understand it requires a good bit more technical knowledge than your average point-and-click consumer router. Luckily, I work in IT for a living and spent roughly 8 years specifically in Network Engineering/Administration at a previous employer (so I'll be fine), but most people without a solid understanding of networking and command line configuration should probably steer clear. Now if only I could get that kind of high-speed connection (I'm assuming you have gigabit fiber) here in the broadband-backwards USA! Any insights into the good stuff that was improved in the latest version?

Count me as another Ubituiti products fan. Recently installed a UniFi AP in the house and love the range as well as the incredible manageability and feature set. Looking to replace my Asus router with an EdgeMax EdgeLite router soon. And running the UniFi controller in a docker just makes it all that much better.

I would also be very interested in this.

FWIW I was unable to get the controller to find my AP also. From what I understand for the AP to automatically find the controller you either need to use the discovery software (like you have on your Mac), or set DHCP option 43 with the inform address of your controller. Once the AP has the inform address and contacts the controller and is provisioned, all works great. I did it the manual way. I ssh'd into the AP and set the inform address manually via the CLI and it showed up immediately in the controller. Also if your AP was already provisioned on another controller (your Mac) you would have had to reset the AP to defaults or "forget" the AP from the controller to find and provision it on another controller. An AP can only be managed by a single controller.

admin / password

Installed the Unifi controller docker, set it up with custom ports (8080 and 8081 were already in use), and switched it to bridge mode. It's working great. Thanks for the work on this!

Was not working for me initially, but after a few tweaks by gfjardim, it's now working great!

Removed the existing docker and container. Reloaded from the new template and it's working great with my HP LaserJet 3015. Thanks a million gfjardim!

Ok. Thanks very much for your efforts in trying to get this to work.

Same error message as before, without the last line. Still unable to login to WebGUI. Found user 'avahi' (UID 105) and group 'avahi' (GID 111). Successfully dropped root privileges. chroot.c: fork() failed: Resource temporarily unavailable failed to start chroot() helper daemon.