Open thoschworks opened 4 years ago
Ugh, seriously?
When did they change it, do you know?
I don‘t know. I stumble upon the problem when I installed the container a few months ago.
@fryfrog Could symlinking /usr/lib/unifi-video/data/videos
to /var/lib/unifi-video/videos
in the container be a solution?
Is changing the path in the Web UI to /var/lib/unifi-video/data/videos still the correct workaround for this? I'm new to docker and I'm moving all my NVRs over to this setup. I haven't noticed any issues in testing either way but I'd like not get bit later.
I haven't been throwing away my container and I used this for the initial run:
docker run
--name unifi-video-test
--restart always
--cap-add DAC_READ_SEARCH
-p 6666:6666
-p 7080:7080
-p 7442:7442
-p 7445:7445
-v /mnt/docker/unifi-video/:/var/lib/unifi-video
-v /mnt/docker/unifi-video/data/videos:/var/lib/unifi-video/data/videos
--tmpfs /var/cache/unifi-video
-e TZ=Europe/Amsterdam
-e PUID=99
-e PGID=100
-e CREATE_TMPFS=no
-e DEBUG=1
pducharme/unifi-video-controller:3.10.13
The container seems to handle power outages and reboots fine. Any issues with doing things this way? Best practices for these types of containers?
As long as you're storing the data outside the container, you're fine. Paths are up to you, so have at it. :)
The image is setup assuming that the recording path is
/var/lib/unifi-video/videos
. This was correct in the past (see Issue #71), but a new installation of the UniFi Video software stores the videos in/usr/lib/unifi-video/data/videos
again (see picture).Solving this problem is IMHO a bit problematic:
I changed the recoding path in the web ui and it works fine.
Perhaps it's the best way to add a note to change the path in the README.md.