aartr

My guess would be setting this option https://motion-project.github.io/motion_config.html#webcontrol_localhost to off will fix that.

Hi Chris, Sorry not sure what happened but I misspelled the repository name. It should be "aartr/docker-motioneye" instead of "aartr/docker-monitioneye". I'll update my post above to include the correct repo name as well.

No, you'll have to go into the Unraid web interface, open the docker tab, click the motionEye icon and select "edit" from the dropdown. In this form find the "Repository" field and change "malvarez00/docker-motioneye" to "aartr/docker-motioneye" and press apply. This should go totally seamless but I'd recommend backing up your "motionEye" folder inside of your appdata just to be safe.

The Chrome issue for motionEye got fixed in the 0.41rc1 release. I have an up-to date docker that can be used as a drop-in replacement here: https://hub.docker.com/r/aartr/docker-motioneye, just change the Repository field to aartr/docker-motioneye

Hey Everybody, I'm hit with these problems as well after upgrading to 6.7. Using the instructions here I got the connection to work again, however I'm using a layer 2 link to connect directly to my local subnet so I can use Bonjour and all that. Now when I connect the connection is successful but I get a random IP address outside of my subnet instead a DHCP-assigned ip on my 10.0.0.0/24 subnet. I'm guessing switching from host to bridge is preventing docker from talking to my network including the DHCP server? I'm not 100% sure what's happening. Am I basically out of luck here? Or is there way to maintain compatibility with layer 2 connections?

I'm guessing there's something wrong in your container's config or your server can't reach dockerhub properly. I just tried and everything seems to be working well for me. I don't have a lot of experience with docker either so I'm afraid I can't help any further.

Hey Steve, Not quite sure what's up. I'd just try to fully remove all the motioneye related containers and do a fresh install. This shouldn't affect your container's config in stored in appdata.

Good to hear! After posting I also updated the container to the latest version of Motion (4.0 -> 4.1.1) and updated MotionEye from 0.39 -> 0.39.1. This required an update to Ubuntu 18.04 as well. Doing so fixed some issues for me with video saving. Stored videos were playing back too fast, updating to Motion 4.1.1 fixed this.

Hi all, I've been able to fix the time zone issue. Seems like the time was off because this docker isn't including the tzdata package (https://github.com/aartrost/Docker-MotionEye/commit/acfd7929ab1a989bcb6c6f0bb48dd991aeb365b8). I've created a fork of this repository that does include this package as a temporary work-around. If somebody is interested you can find it here: https://hub.docker.com/r/aartr/docker-motioneye/. To apply this fix to your own unraid docker container, just edit the docker container config and update the Repository field to aartr/docker-motioneye . Hopefully malvarez00 can update the official docker with this minor change so that everybody will get the fix automatically.