jennettwheeler/motioneye repository overview

A motioneye container featuring linuxserver's architecture :-

• easy user mappings (PGID, PUID)
• custom base image with s6 overlay
• uses a base OS that has weekly updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
• however, these images are only updated when new motioneye releases are available

⁠jennettwheeler/motioneye⁠

Motioneye⁠ - A web frontend for the motion daemon.

⁠Version Tags

This image provides various versions that are available via tags. latest tag usually provides the latest stable motioneye version.

⁠Usage

Here are some example snippets to help you get started creating a container.

⁠docker

docker create \
  --name=motioneye \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -e UMASK_SET=022 `#optional` \
  -p 8765:8765 \
  -p 8081-8099:8081-8099 `#optional`\
  -v <path to config>:/config \
  --restart unless-stopped \
  jennettwheeler/motioneye

⁠docker-compose

Compatible with docker-compose v2 schemas.

---
version: "2"
services:
  motioneye:
    image: jennettwheeler/motioneye
    container_name: motioneye
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - UMASK_SET=022 #optional
    volumes:
      - <path to config>:/config
    ports:
      - 8765:8765
      - 8081-8085:8081-8085 #optional
    restart: unless-stopped

⁠Parameters

Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

⁠Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__PASSWORD=/run/secrets/mysecretpassword

Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.

⁠User / Group Identifiers

When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

⁠Application Setup

Access the webui at <your-ip>:8765, for more information check out Motioneye⁠.

⁠Support Info

• Shell access whilst the container is running: docker exec -it motioneye /bin/bash
• To monitor the logs of the container in realtime: docker logs -f motioneye

⁠Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup⁠ section above to see if it is recommended for the image.

Below are the instructions for updating containers:

⁠Via Docker Run/Create

• Update the image: docker pull linuxserver/motioneye
• Stop the running container: docker stop motioneye
• Delete the container: docker rm motioneye
• Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
• Start the new container: docker start motioneye
• You can also remove the old dangling images: docker image prune

⁠Via Docker Compose

• Update all images: docker-compose pull
  • or update a single image: docker-compose pull motioneye
• Let compose update all containers as necessary: docker-compose up -d
  • or update a single container: docker-compose up -d motioneye
• You can also remove the old dangling images: docker image prune

⁠Via Watchtower auto-updater (especially useful if you don't remember the original parameters)

• Pull the latest image at its tag and replace it with the same env variables in one run:

  docker run --rm \
  -v /var/run/docker.sock:/var/run/docker.sock \
  containrrr/watchtower \
  --run-once motioneye
  

  Copy

Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.

• You can also remove the old dangling images: docker image prune

⁠Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://[email protected]/jennett-wheeler/motioneye.git
cd motioneye
docker build \
  --no-cache \
  --pull \
  -t jennett-wheeler/motioneye:latest .

⁠Versions

• 2020-02-26: - Removed file processor (might make separate docker image) and updated to use latest lsiobase alpine image.
• 2020-01-03: - Update to Motioneye 0.42 & add file processor to reduce file space.
• 2019-10-08: - Initial Release with Motioneye 0.41.