multiple camera support with docker

This commit is contained in:
Cédric Verstraeten
2016-10-25 08:38:31 +02:00
parent 859e8ed246
commit 74a221d82f
3 changed files with 35 additions and 3 deletions

View File

@@ -48,12 +48,12 @@ Kerberos.io comes with **a bunch of features**, below you can find a short list
* Fluent and responsive overview of snapshots by day and hour.
* System information (CPU, disk, network, etc).
* View you activity everywhere with kerberos.io cloud.
* Multiple cameras with Docker or Raspbian.
* ..
Features **NOT** included:
* Video recording (only snapshots are taken); third-party solutions are available (IP camera viewer).
* Multiple camera support; not supported out-of-the-box, but it's possible with some technical skills.
<a name="installation"></a>
## Installation

View File

@@ -9,14 +9,16 @@ Create a **docker-compose.yml** file and following configuration:
machinery:
image: kerberos/machinery
ports:
- "8889:8889"
- "8889"
web:
image: kerberos/web
ports:
- "80:80"
- "80"
volumes_from:
- machinery
links:
- machinery
Run following command; this will download the Kerberos.io docker images and configure them properly.

View File

@@ -0,0 +1,30 @@
# Multi-camera with Docker
If you own multiple IP-cameras, then you probably **don't want** to setup **a Raspberry Pi for each camera**. Thanks to Docker there is an easier approach: instead of running multiple machines you can run multiple containers on a single machine. And when you're processing a lot of cameras, you can **distribute the cameras/containers across multiple machines** by using **Docker Swarm**.
## This is how it goes..
The approach is equal to [**the traditional Docker approach**](/installation/docker). First you need to make sure you have **Docker installed** on the machine(s) you prefer. After the installation you can use docker-compose to get Kerberos.io up and running. Create a **docker-compose.yml** file and add following configuration:
machinery:
image: kerberos/machinery
ports:
- "8889"
web:
image: kerberos/web
ports:
- "80"
volumes_from:
- machinery
links:
- machinery
Instead of running docker-compose up, we add an additional parameter **-p**. This will create and link the containers from the compose file, but will **wrap and isolate** the containers **in a project**. By reusing this command, and defining different project names, you can run multiple Kerberos.io instances on the same machine (or distribute them over multiple machines.)
docker-compose -p camera-frontdoor up -d
docker-compose -p camera-partyroom up -d
...
docker-compose -p camera-garden up -d