Public | Automated Build

Last pushed: 3 months ago
Short Description
Motioneye in a docker!
Full Description

Motioneye Docker

A surveillance solution base on
MotionEye
Motion and Docker.

It's easy and ready to use. Just plug in a webcam and run this docker, then
videos and images will be saved once a motion is detected while a notification
e-mail including the recorded video and a preview image will be sent. On top of
that, the webcam can be accessed anytime via HTTP live streaming.

Quick Start

Clone this project then cd into it:

git clone https://github.com/jshridha/docker-motion
cd docker-motion

Build or pull the image

Then build your own dockmotion Docker image:

docker build -t motioneye .

Note that a pre-built image is also available:

docker pull jshridha/motioneye:latest

Run the container with configs , e.g.,

docker run -d --name=motioneye \
    --device=/dev/video0
    -p 8081:8081 \
    -p 8765:8765 \
    -e TIMEZONE="America/New_York" \
    -e PUID="99" \
    -e PGID="100" \
    -v /mnt/user/appdata/motioneye/media:/home/nobody/media \
    -v /mnt/user/appdata/motioneye/config:/config \
    jshridha/motioneye:latest

Note that:

  • The --device flag should be replaced by your webcam's device ID.
  • Set the PUID and PGID enviornmental variables to match those of the user and group to run the app (optional, default is PUID=99 and PGID=100)
  • Expose port 8765 to access the motioneye interface
  • Expose port 8081 to access the motion api - make sure you replace "webcontrol_localhost on" with "webcontrol_localhost off" in motion.conf

  • Mount a volume /config to persist the configuration

  • Mount a volume to /home/nobody/media to persist the media (webcam image stills)

Screenshots

  • E-mail Notification

  • HTTP Live Streaming

Docker Pull Command
Owner
jshridha
Source Repository

Comments (1)
flar
a year ago

Hi! Could use an advice. If i connect my ip camera within MotionEye interface, it does understands what it is, does require user\pass, and passes it, BUT, when this camera added, motion fails, here`s the container logs
http://pastebin.com/fLBggV2C

What could it be? Separately-builded motion-container are able to connect to that camera, give me stream, motion detection, timeleaps, etc. What should i check here?

In any case - thanks for the image :)