fryfrog

Will do!

Done. It looks like they did some fiddling w/ their unifi-video bash script because I had to re-create the patch we apply to it. Please let us know if it doesn't work! It *builds*, but I'm not gonna test it on my setup!

You know Docker containers don't update themselves, right? You need to `docker pull` them and restart, or what ever the work flow is in unRAID for doing that. Check out https://hub.docker.com/r/pducharme/unifi-video-controller/ where you can look at the Dockerfile and Build Details and see that it is up to date. My own personal instance is also 3.9.8, so I know it is working. Good luck!

It is updated, do you not see the update?

I have been supporting as I can, like I do for a number of other projects.

Sorry about that, I updated beta awhile ago and then pushed it to master, but totally forgot to push it to release and then tag it.

@blista99: ^ This tells me you might be trying to pass in the wrong UID and GID. Those are root's UID/GID, which you shouldn't use. Create a user and group, probably unifi-video:unifi-video and use that. Make sure it owns the config and video directory you want to use. Probably related to trying to run it as root / uid/gid 0. But could be other things. Can you post your Docker run command? You should replicate that which is in the github README.md using what ever system QNAP lets you. https://github.com/pducharme/UniFi-Video-Controller/

@Can0nfan: The :beta tag is building now w/ new baseimage and 3.9.8 beta 3, let me know how it goes. @CorneliousJD: I use it on Arch Linux, it should work fairly well just about anywhere. About the only thing unRAID specific is the example UID/GID.

@Can0nfan, I'll make sure the beta gets updated today. Didn't realize one had come out. For Protect, they're doing their own Docker, so I imagine we won't need to.

Looks like a few places have uneditable IPs, now that I go look. But the setting I was thinking of is the per-camera setting for the host controller, as seen at

https://hub.docker.com/r/pducharme/unifi-video-controller/ ^ The docker hub entry show DAC_READ_SEARCH and SYS_ADMIN. I *think* SYS_PTRACE is for using strace inside, you can probably drop that. I'm not sure what the SETGID and SETUID do, but if you google them you can probably find out. I bet you can remove them. Same for NET_BIND_SERVICE. Do them one at a time over a few hours or days to be sure, you can probably get rid of all of them except those mentioned as needed. That is all I run w/, though I don't have disks spinning down.

I never did figure out what/how the discovery works, I think it must be some sort of multicast thing? You can flop it into host/bridge network mode for the adoption, then afterward flop it out. You can also load up the camera's UI and set the adoption IP / hostname. If you go that route, you'll also need to change that one setting in the controller. It gets populated w/ the 172 address that internal docker uses, but should of course be the hosts real ip.

*Probably* in your /mnt/user/appdata/unifi-video/ there is a logs directory. Or data/logs directory. Look in there for log output from the daemon itself. The Docker output would just be from the initialization and startup scripts.

@kbb2002, oh sorry you're talking about the unifi docker, not unifi-video. I don't know that one enough to comment on what the problem might be. What you've shown me looks like I'd expect on the surface, so you'll have to dig deeper and/or hope for some unifi help from someone who uses it.

@David Bott, you shouldn't update *inside* a container, it is against the docker way. But it was updated a day or two after it came out, so you just need to `docker pull pducharme/unifi-video-controller` or how ever else you update your docker containers. @kbb2002, it sounds like you're *not* passing in a volume for the configs to be stored in. Anything *inside* the container is wiped at upgrade (and restart, depending on settings). What does your `-v <data dir>:/var/lib/unifi-video` look like?

That is the container log, which doesn't have a lot of output (though you can turn on verbose/debug). Check the unifi-video logs, they'll be in maybe `data/logs` of your volume. There are a few, you can `ls -ltr` to see the recently modified ones, but `server.log` should be one.

Check your logs, see what it is doing.

In 3.9.2 the changed paths around a little bit, but I don't think that'd impact cameras showing up. I recently setup this docker from zero w/ fresh cameras and had to switch to `--net host` for the auto detection portion of both adding to cloud *and* to get cameras to show up auto-magically. I flipped it back afterward, but would like to see if I can figure out why it didn't work right. Maybe a port we've missed?

@brewDuck, your docker-compose.yml looks weird to me, though I don't use it myself. For example, you have 4 volumes when only 2 are needed. Assume the format is outside:inside, there are some oddities. What is /usr/lib/unifi-video/work and /usr/lib/unifi-video/ext ? Maybe that is the old one? Try the new one https://github.com/pducharme/UniFi-Video-Controller/blob/master/docker-compose.yaml and see how it does.

It is literally in the post right before this. You should check out your server.log and other logs before you blindly roll back.

I literally both use this for my unifi-video setup and maintain the docker image with pducharmes, you can pull at any time and it'll be working and stable. We even went a little further and moved to a "release" branch, so now it only gets updated when we do it manually. All the fixes and changes to into master first, only going to release after we've tested them. We also started tagging releases, so you can at any time add ":3.9.2" for example and get back to it. So for this 3.9.3 update, you're on ":latest". If it went wonky, you could just do the pull w/ ":3.9.2" at the end and go back (or w/ the last shittyness as an example, ":3.9.0". Anyway, you should feel safe doing the pull and restarting. 90% of the time it'll be fine 100% of the time!

You can just `docker pull pducharme/unifi-video-controller` any time, if there is an update it'll get it. If there isn't, it won't. You could also watch https://hub.docker.com/r/pducharme/unifi-video-controller/builds/ or https://github.com/pducharme/UniFi-Video-Controller/commits/release

I think `server.log` is where I'd start.

I assume if you live view the cameras, it works? Or the grid view? Have you checked the logs for errors? What are you passing in for data and video paths?

If the software is running and you see the cameras and their feeds, you should be able to record. What do you mean when you say it doesn't record? Do you set the cameras to always record? Record on motion?