coppit

I thought I fixed that. Can you make sure you're running the latest version? If you go to the docker page, there might be an "update" option next to the container. If not, click on the advanced view in the upper right, then do force update on the container.

You can also mount your cache drive, or wherever you put the config dir.

I'm confused by this. When you run it the first time, it creates the config file and exits. You then need to edit the config file to set the password. Then restart the container. Are you saying that doing this results in an error? Can you share that message? When you use bridge networking, use the IP address of your server to connect. Also be sure that you're passing the port 8090 through. Attached is what my setup looks like in the Docker panel. So in my case, I connect to 192.168.1.100, port 8090. P.S. congrats on being the first to try this!

No, sorry. To be honest I'm a bit of an SNMP noob, and just got the basics working for Observium.

Sounds awesome. Will do.

https://forums.lime-technology.com/topic/56659-xeoma-surveillance-software

Xeoma is surveillance software. It has low CPU usage (about 3% CPU when idle) and an easy-to-use user interface. I tried ZoneMinder, which was very clunky to use, and had very high CPU usage. For about a year I ran Blue Iris in a Windows VM, but after SageTV and AirVideo HD were running in containers, Blue Iris was the only thing left in the VM. Blue Iris was routinely using 30-40% of a CPU, so I was happy that Xeoma had a docker-izable Linux server. The container will be available in community applications shortly. After configuring and launching the container, download the software from their website for your computer. The Mac and Windows versions are identical, but the iOS app doesn't let you configure things. You can try Xeoma for free using the trial version, but it will be somewhat crippled. Note that the free version won't work, since it can't connect to the server. For more information on usage, including how to connect your cameras: https://hub.docker.com/r/coppit/xeoma/ For source code: https://github.com/coppit/docker-xeoma

HandBrake is a video encoder. This container supports a GUI (RDP or web browser access) as well as a fully automated watch folder. The container will be available in community applications shortly. Put "--cap-add=SYS_NICE" into the "extra parameters" in the advanced settings of the container to allow HandBrake to be run at a lower priority. Fully automated conversion: Drop files into the /watch directory, and they will be encoded into the /output directory. Interactive user interface: Point your web browser to your server, port 8080, or point a remote desktop client to port 3389. Find your files in /media, and put the converted file in /media or /output. For more information on usage: https://hub.docker.com/r/coppit/handbrake/ For source code: https://github.com/coppit/docker-handbrake Note: I'm releasing this while sparklyballs reviews my pull requests. I will delete this container after those pull requests are accepted, to avoid unnecessarily forking the container space.

Yeah, for some reason it's trying to put the file into / instead of /output. You can check your volume mapping this way: docker exec FileBot ls /output If it is, then check your filebot.sh file, making sure that the filebot command at the end has "--output /output"

What driver is that? Realtek HD audio? Huh, never tried that. Thanks for the tip.

I know it's a weak data point, but at work, with Intel CPUs and Xen, we had to disable C-states to work around some lockups.

Hi sparklyballs, Do you think you might be able to take a look at the pull requests I submitted for your HandBrake docker container? https://github.com/sparklyballs/desktop-dockers/pulls I tried to keep them independent, but there will be a little bit of conflict resolution that you'll need to do if you decide to take them all. Sorry about that. BTW, I'll take another pass over the README if everything gets integrated.

Does your password have fancy characters like $"! or ' ? If so, you'll want to put it in either single quotes or double quotes, whichever you aren't using. And if you're using both, I'll have to give you special instructions. What does the log say?

Hi all, I just pushed a big update to this container. I rewrote the event handling code, and hopefully it's more robust now. Let me know if you see any issues!

For some reason your machine can't talk to itself. What happens if you log into the server and run "ping localhost"? If that works, try "curl -I http://localhost/" (that's a capital eye, not an el). It should say "Server: emhttp" on the second line.

I gave up on it too. I checked out ZoneMinder again, got it working, got annoyed by the high CPU usage, and gave up on it. I also looked at MotionEye, but it had even worse CPU usage. The best turned out to be Xeoma. Super low disk usage and CPU usage, and easy interface. I'll release a Docker container and template for it in a day or two.

Yeah! I updated the meta data, and dropped a few references to noip2 and noip and no-ip into the description. Hopefully something works. I also updated my top post to tell people to search for "coppit" first. I looked into making the path always show up in the template page, but that appears to be a feature of the new XML format that is only supported by 6.2. I'd rather not leave pre-6.2 out in the cold, so I'll have to leave that as it is. Dang. You found (hopefully) the one scenario I didn't test for. Congrats! I just pushed a fix that simplifies and generalizes the code. It should fix the problem for you.

I just deleted my container. I then re-created it from Community Applications. When I was done, there was a new folder /mnt/cache/appdata/No-Ip. Further, if I clicked "Show advanced settings..." before applying the template (or by clicking the container after it is created), I see the path right there. I suppose I could make the folder path an "always show" configuration value. But I'm not sure what you mean about there not being a path in the standard location. Can you elaborate? Are you creating the container on the command line or something?

Did you follow the link in the first post? It says: Let me know if anything is unclear.

I played with it a bit. In the web container, it's trying to connect to the machine using the dns name "machinery". I guess that's a docker compose thing. To hack it, I did docker exec -it KerberosWebDocker bash echo "192.168.1.100 machinery" >> /etc/hosts service nginx start Then I was able to go to http://192.168.1.100:780/. I could enter the rtsp:// URL for my camera, and get a live stream. But I couldn't get motion detect to work. And you only get 1 camera per machinery+web container pair. Oh, also, I temporarily mapped my appdata config dir to a different path inside the machinery container, then did the "docker exec" thing to get inside the container and copy the config files into my new path. Then reassigned my host dir to the normal /etc/opt/kerberos/config path inside the container. I don't know if having those config files helped or not... I figured that "hiding" them with the container volume mapping wasn't helping things...

Hey, I'm interested in this. I can help too. What's the status?

I'm no expert on this, but the HDHomeRun Prime brags about supporting CableCard. And the SageTV user (and apparently UNRAID user) "fuzzy" has this in his signature: unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers.Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA.Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189SOther Clients: Mi Box in Master Bedroom, HD-200 in kids room Unfortunately I don't know what his userid is on these forums or I'd page him. :-)

Thanks for doing this. I took a look at it, and I like the simplicity of the web-based MotionEye UI, and the "just works" motion detection. (detect motion, save a second before until the motion stops.) My problem with it is that Motion converts the h264 stream to JPEG, does the analysis, and reconverts it back to h264. Horribly inefficient, if you ask me. I had a CPU core going between 20% and 80% at all times. Ug! FYI, it looks like the main repository has died, and all the action is over in Motion-Project on github. I'm not sure which version of motion you're installing, but you might want to consider the 4.0.1 version that they've released. https://github.com/Motion-Project/motion/releases/tag/release-4.0.1

Hey sparkly, I noticed a couple of things with the inotify folder watcher: 1) If I add another file while the first one is being converted, the 2nd file doesn't get converted. I think the notification message is being lost. 2) If I add another file after the first one is done being converted, it starts re-converting the first, then works on the second. I'm thinking about working on this, integrating some of the work I did for FileBot's watch folders. Some details are here: https://github.com/coppit/docker-inotify-command. (Now that I think about it, my code might be susceptible to issue #1 as well, so I'll fix that too.) For issue #2, I was thinking about creating a file that "remembers" the files that have already been processed. How does all that sound? If it's good, I'll work on it and send you some pull requests.

Just to throw another option out there... SageTV. For me, it has the best UI for PVR and a personal library of media. With the release of the source last year, we now have a new version 9. If you can get your hands on an Extender (ebay?), you have a very nice set-top box. So here's my setup: HDHomeRun with an Antenna to capture HD over-the-air and convert it to MPEG 3TB drive mounted with Unassigned Devices Docker container running SageTV server, passing the mounted 3TB in for recordings. Configured the HDHomeRun as the PVR input, and to snarf in my media library from /mnt/user/Media. SageTV extender from like 2007 in the living room. SageTV clients on computers. I converted over from a VM to the Docker container this weekend, and it was easy-peasy. Man, I remember buying custom HTPC cases for SageTV back in like 2004. Downsides: the extenders aren't for sale from Frey, since they were bought by Google. SageTV isn't very strong on streaming media, but hopefully that will catch up now that it's open source.