Giter VIP home page Giter VIP logo

kerberos-docker's Introduction

Kerberos Open Source - Docker (Archived)

This project is archived, and move to the new agent repository: Kerberos Agent.


Build Status Join the chat

License

The Kerberos Open Source project is licensed with BY-NC-SA 4.0, this means that everyone can use Kerberos and modify if to their needs, in a non commercial activity.

More information about this license.

Why Kerberos?

As burglary is very common, we believe that video surveillance is a trivial tool in our daily lifes which helps us to feel a little bit more secure. Responding to this need, a lot of companies have started developing their own video surveillance software in the past few years.

Nowadays we have a myriad of expensive cameras, recorders, and software solutions which are mainly outdated and difficult to install and use. Kerberos Open Source goal is to solve these problems and to provide every human being in this world to have their own ecological, affordable, easy-to-use and innovative surveillance solution.

Docker

A Docker image (x86, ARMv7, ARMv8) is available on the Docker Hub, which contains all the necessary software to setup the Kerberos agent. Before you can run this image you will have to make sure Docker is installed. After the installation you can use docker run to get the Kerberos agent up and running; you can also opt for dockeros to create and scale your Kerberos agents.

Use docker run

After you've installed Docker, you can open a command prompt and type in following command. This will pull the kerberos image and make the web interface available on port 80 and the livestream on port 8889. You can give the container a custom name using the --name property.

docker run --name camera1 -p 80:80 -p 8889:8889 -d kerberos/kerberos
docker run --name camera2 -p 81:80 -p 8890:8889 -d kerberos/kerberos
docker run --name camera3 -p 82:80 -p 8891:8889 -d kerberos/kerberos

Or use dockeros (our docker creation tool)

We've created a simple and small tool to auto provision and auto configure the Kerberos agents. The idea is that you define the different configurations for every camera upfront (/environments directory), and map them to into your Docker container (using volumes). The ultimate goal is to have a fully automated for provisioning your Kerberos agents in just a matter of seconds. It's also a great way to backup your security configuration.

CAMERA 1 <<== CONTAINER1 <<== environment/cameraconfig1
CAMERA 2 <<== CONTAINER2 <<== environment/cameraconfig2
CAMERA 3 <<== CONTAINER2 <<== environment/cameraconfig3

How to use it?

The tool we've created is a simple bash script which we called dockeros, and exposes a couple of methods; discussed below. By specifying a number of parameters, dockeros will do all the magic dockering for you. This tool is still work in progress, so PR's and new features are welcome!

git clone https://github.com/kerberos-io/docker
cd docker/bin
./dockeros.sh {command}

Commands

List all kerberos.io containers which are created.

./dockeros.sh showall

Remove all kerberos.io containers which were created before.

./dockeros.sh cleanup

Create a kerberos.io container with a name and predefined configuration.

./dockeros.sh create {name} {config} {webport} {streamport}
  • name: This is the name of the container which will be created.

  • config: The configuration which needs to be injected in the container. The configuration directories can be found in the /environments folder.

  • webport: The port on which the webinterface will be served.

  • streamport: The port on which the livestream will be served.

Buildx

docker run --rm --privileged docker/binfmt:66f9012c56a8316f9244ffd7622d7c21c1f6f28d

docker buildx create --name nubuilder --driver docker-container

docker buildx use nubuilder

docker buildx inspect --bootstrap

# linux/arm/v6 gives issues on php7.1
docker buildx build --platform linux/amd64,linux/arm/v7,linux/arm64 -t kerberos/kerberos --push .

kerberos-docker's People

Contributors

berezovskyi-oleksandr avatar cedricve avatar davidjb avatar flaviostutz avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

kerberos-docker's Issues

Dashboard does not show stream, if host streaming port set to anything other than 8889

Intro:

I am a subscribed member, with seven cameras currently streaming to kerberos-cloud. I use Podman on RHEL8, with SELINUX enabled.

Issue:

When I configure a single camera and map internal port 8889 to external port 8889, I am able to both see the stream on http://SERVER:8889 and via the Dashboard screen of the web app.

eg. (stream works on port 8889 and in Dashboard)

podman create --name=kerberos-camera5 \
    -p 80:80 \
    -p 8889:8889 \
    --security-opt label=type:kerberos.process \
    -v "/opt/kerberos-camera5/config":"/etc/opt/kerberosio/config":Z \
    -v "/XFS0/kerberos-camera5/capture":"/etc/opt/kerberosio/capture":Z \
    -v "/opt/kerberos-camera5/logs":"/etc/opt/kerberosio/logs":Z \
    -v "/opt/kerberos-camera5/webconfig":"/var/www/web/config":Z \
    docker.io/kerberos/kerberos:latest 

BUT when I set the streaming port to something else (eg. 8885), I am able to see the stream on http://SERVER:8885, but the stream never loads on the dashboard:

eg. (stream works only via port 8885)

podman create --name=kerberos-camera5 \
    -p 85:80 \
    -p 8885:8889 \
    --security-opt label=type:kerberos.process \
    -v "/opt/kerberos-camera5/config":"/etc/opt/kerberosio/config":Z \
    -v "/XFS0/kerberos-camera5/capture":"/etc/opt/kerberosio/capture":Z \
    -v "/opt/kerberos-camera5/logs":"/etc/opt/kerberosio/logs":Z \
    -v "/opt/kerberos-camera5/webconfig":"/var/www/web/config":Z \
    docker.io/kerberos/kerberos:latest 

This issue will affect anyone with more than one camera, who is separating container access by port (as per the documentation).

Workaround

I found that if persistent storage has been configured, then the following workaround can be used:

  1. Assuming that the desired streaming port is 8885, the host and container ports are both be set to 8885:
podman create --name=kerberos-camera5 \
    -p 85:80 \
    -p 8885:8885 \
    --security-opt label=type:kerberos.process \
    -v "/opt/kerberos-camera5/config":"/etc/opt/kerberosio/config":Z \
    -v "/XFS0/kerberos-camera5/capture":"/etc/opt/kerberosio/capture":Z \
    -v "/opt/kerberos-camera5/logs":"/etc/opt/kerberosio/logs":Z \
    -v "/opt/kerberos-camera5/webconfig":"/var/www/web/config":Z \
    docker.io/kerberos/kerberos:latest 
  1. The container's /etc/opt/kerberosio/config/stream.xml configuration file is modified as follows:
# Change this:
<streamPort type="number">8889</streamPort>
# To this:
<streamPort type="number">8885</streamPort>
  1. Restart the container and both the 8885 stream and Dashboard stream will now work.

resource.error: (1, 'Operation not permitted') when trying to run docker image

OS is Ubuntu 20.04.
Running on a Raspberry pi 4 4GB.

Unfortunately it seems the docker image is doing something docker or Ubuntu isn't allowing. When running sudo docker run -p 80:80 -p 8889:8889 kerberos/kerberos the following output is observed and the container stops:

Config files are available.
Config files are available.
Traceback (most recent call last):
File "/usr/bin/supervisord", line 11, in
load_entry_point('supervisor==3.3.1', 'console_scripts', 'supervisord')()
File "/usr/lib/python2.7/dist-packages/supervisor/supervisord.py", line 365, in main
go(options)
File "/usr/lib/python2.7/dist-packages/supervisor/supervisord.py", line 375, in go
d.main()
File "/usr/lib/python2.7/dist-packages/supervisor/supervisord.py", line 70, in main
rlimit_messages = self.options.set_rlimits()
File "/usr/lib/python2.7/dist-packages/supervisor/options.py", line 1372, in set_rlimits
soft, hard = resource.getrlimit(res)
resource.error: (1, 'Operation not permitted')

Doesn't start

Following http://www.kerberos.io/opensource/installation#docker :

> docker pull kerberos/kerberos

Using default tag: latest
latest: Pulling from kerberos/kerberos
Digest: sha256:630acdf5b8fae7cbb5f0a17cbc2f326f87efedd0db1e6709365e4419058a8714
Status: Image is up to date for kerberos/kerberos:latest
docker.io/kerberos/kerberos:latest

> docker run --name camera1 -p 80:80 -p 8889:8889 -d kerberos/kerberos

1878e9a752e456fea188db61cc3e9c659074600ad9ed42e214c7bccf7288a62c

> docker logs camera1

/runny.sh: line 15: /etc/php/7.0/fpm/pool.d/env.conf: No such file or directory
/runny.sh: line 16: /etc/php/7.0/fpm/pool.d/env.conf: No such file or directory
/runny.sh: line 17: /etc/php/7.0/fpm/pool.d/env.conf: No such file or directory
php7.0-fpm: unrecognized service
2020-01-03 19:34:15,771 INFO Set uid to user 0 succeeded
2020-01-03 19:34:15,778 INFO RPC interface 'supervisor' initialized
2020-01-03 19:34:15,778 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2020-01-03 19:34:15,778 INFO supervisord started with pid 15
2020-01-03 19:34:16,781 INFO spawned: 'nginx' with pid 19
2020-01-03 19:34:16,785 INFO spawned: 'machinery' with pid 20
2020-01-03 19:34:16,801 INFO exited: nginx (exit status 1; not expected)
2020-01-03 19:34:17,804 INFO spawned: 'nginx' with pid 23
2020-01-03 19:34:17,805 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-03 19:34:17,825 INFO exited: nginx (exit status 1; not expected)
2020-01-03 19:34:20,808 INFO spawned: 'nginx' with pid 24
2020-01-03 19:34:20,831 INFO exited: nginx (exit status 1; not expected)
2020-01-03 19:34:24,814 INFO spawned: 'nginx' with pid 25
2020-01-03 19:34:24,832 INFO exited: nginx (exit status 1; not expected)
2020-01-03 19:34:25,812 INFO gave up: nginx entered FATAL state, too many start retries too quickly

When I now visit http://localhost:80/ I get ERR_CONNECTION_RESET

SSL Scheme

Turns out, while using a reverse proxy, assets are loaded through http still, is it possible to set a flag "ssl: true" in the docker-compose file ?

ulvad3xqp2qeqyae13qenuanb

502 Bad Gateway - No streaming

After using the latest docker image, it appears that Kerberos doesn't work. Adding an IP camera provides nothing and a message with "No stream, is the machinery running?" After using the console inside Chrome to inspect potential issues, the result was: GET http://whirlpool/stream 502 (Bad Gateway).

The docker container was created using docker run --name camera1 -p 80:80 -p 8889:8889 -d kerberos/kerberos after executing docker pull kerberos/kerberos:latest

Kerberos docker images not working

I've set up the kerberos.io docker image as follows:

$ cat docker-compose.yml
machinery:
    image: kerberos/machinery
    ports:
    - "8889"

web:
    image: kerberos/web
    ports:
    - "80"
    volumes_from:
    - machinery
    links:
    - machinery

$ sudo docker-compose up
Recreating kerberos_machinery_1
Recreating kerberos_web_1
Attaching to kerberos_machinery_1, kerberos_web_1
machinery_1 | 2017-01-05 22:09:01,015 CRIT Set uid to user 0
machinery_1 | 2017-01-05 22:09:01,055 INFO RPC interface 'supervisor' initialized
machinery_1 | 2017-01-05 22:09:01,057 CRIT Server 'unix_http_server' running without any HTTP authentication checking
machinery_1 | 2017-01-05 22:09:01,057 INFO supervisord started with pid 6
web_1       | 2017-01-05 22:09:01,384 CRIT Set uid to user 0
web_1       | 2017-01-05 22:09:01,424 INFO RPC interface 'supervisor' initialized
web_1       | 2017-01-05 22:09:01,426 CRIT Server 'unix_http_server' running without any HTTP authentication checking
web_1       | 2017-01-05 22:09:01,426 INFO supervisord started with pid 6
machinery_1 | 2017-01-05 22:09:02,061 INFO spawned: 'machinery' with pid 9
web_1       | 2017-01-05 22:09:02,430 INFO spawned: 'php5-fpm' with pid 9
web_1       | 2017-01-05 22:09:02,439 INFO spawned: 'nginx' with pid 10
machinery_1 | 2017-01-05 22:09:03,064 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
web_1       | 2017-01-05 22:09:03,519 INFO success: php5-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
web_1       | 2017-01-05 22:09:03,520 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

I can see the two containers running:

$ sudo docker ps
CONTAINER ID        IMAGE                COMMAND               CREATED             STATUS              PORTS                            NAMES
489650de249f        kerberos/web         "/bin/bash /run.sh"   3 minutes ago       Up 3 minutes        443/tcp, 0.0.0.0:32772->80/tcp   kerberos_web_1
f1b26bb71054        kerberos/machinery   "/bin/bash /run.sh"   3 minutes ago       Up 3 minutes        0.0.0.0:32771->8889/tcp          kerberos_machinery_1

I can login into the web interface, but this is what I get:

screenshot from 2017-01-05 22-23-02

screenshot from 2017-01-05 22-24-15

I went into the settings panel and tried to set up an IPCamera pointing it to http://user:[email protected]/video.cgi (I've confirmed this mjpg stream works from my browser) but nothing shows up in the logs.

Any hints on how I can troubleshoot this? (Thanks in advance!)

Docker container dies immediately on Raspberry Zero

pi@pi-zero-w:~ $ sudo docker start camera1
2020-02-09T20:53:58.340074224Z network connect 68c43e2bab7308ed42fbf78d10f81317e404e7e69454c3778077f8f168a1d63a (container=0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3, name=bridge, type=bridge)
2020-02-09T20:53:58.379730165Z volume mount 9c28d6d5b3bfe657ab416ab414ca585657bc8a6d2ecbf0dd252aa5c0f09cfa71 (container=0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3, destination=/etc/opt/kerberosio/capture, driver=local, propagation=, read/write=true)
2020-02-09T20:53:58.380225164Z volume mount a2665ad5fd450b87d43a12ac397c12d7d1c420773d4c0801fbfe998a31460c43 (container=0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3, destination=/etc/opt/kerberosio/config, driver=local, propagation=, read/write=true)
2020-02-09T20:53:58.380707163Z volume mount dab942a5b901f5024570eef77e7227f22c366ef0f396352209b9082993048124 (container=0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3, destination=/etc/opt/kerberosio/logs, driver=local, propagation=, read/write=true)
2020-02-09T20:53:58.381287162Z volume mount 9c0dd533d2afc565ec22f6f8ad08ef27d05103f4ebf0e8877f285b8897bc8306 (container=0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3, destination=/var/www/web/config, driver=local, propagation=, read/write=true)
camera1
2020-02-09T20:54:03.377042665Z container start 0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3 (image=kerberos/kerberos, name=camera1)
pi@pi-zero-w:~ $ 2020-02-09T20:54:04.389089139Z container die 0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3 (exitCode=139, image=kerberos/kerberos, name=camera1)
2020-02-09T20:54:05.106594056Z network disconnect 68c43e2bab7308ed42fbf78d10f81317e404e7e69454c3778077f8f168a1d63a (container=0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3, name=bridge, type=bridge)
2020-02-09T20:54:05.247325843Z volume unmount 9c28d6d5b3bfe657ab416ab414ca585657bc8a6d2ecbf0dd252aa5c0f09cfa71 (container=0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3, driver=local)
2020-02-09T20:54:05.253083835Z volume unmount a2665ad5fd450b87d43a12ac397c12d7d1c420773d4c0801fbfe998a31460c43 (container=0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3, driver=local)
2020-02-09T20:54:05.254248833Z volume unmount dab942a5b901f5024570eef77e7227f22c366ef0f396352209b9082993048124 (container=0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3, driver=local)
2020-02-09T20:54:05.260828823Z volume unmount 9c0dd533d2afc565ec22f6f8ad08ef27d05103f4ebf0e8877f285b8897bc8306 (container=0e3af8316239296ba8956e488086805d4978b418ce15096655368110942b54e3, driver=local)

High CPU Usage On Virtualized Server

Hi,

Like other users I am having extremely high CPU usage (50%+) when running basically anything. I am running 3 cameras at 1920x1080/20fps on a Ubuntu LTS 20.01 server via Proxmox. If I restart the containers and never touch the portal they will run fine (15-20%) but the second I try to access the portal and look at settings or streams it jumps straight to 50%+ usage.

TCPSocket output to server on host doesn't work?

Hi,
My setup with issue is:

  • Windows 10 Home with WSL2 + Docker desktop for windows set for Linux containers.
  • Kerberos docker works as expected with alerts output to "Video" and "MQTT" (to a test MQTT server http://www.dioty.co/).
  • Simple TCP server on host (the windows 10 machine)

I've set the IP on the kerberos machinery TCPSocket setup as "host.docker.internal" and also as the IP I've seen allocated to the WSL2 by the Winodws OS (i.e. 172.30.128.1 through ipcconfig). None worked.

To verify the idea of using "host.docker.internal" or the WSL2 IP, I then run a simple alpine docker with the following commands:

 # apk add curl
 # curl http://host.docker.internal:1337

It worked and the connection data appeared on my simple TCP server.

So what am I missing here with Kerberos.io docker?

Test setup where TCPSocket works as expected:

  • RaspberryPi 3B with kerberos.io image. The TCPSocket ip is set to the IP of the windows machine (192.168.1.21)
  • Simple TCP server on the windows 10 machine

p.s.
I'm totally noob with Docker - I have literally less than 2 days experience at the moment...

Unable to docker-compose the docker-compose.yml

Hi,
I am a newbie. I learn to install and run kerberosio on top Docker on my Raspberry Pi B.
Unfortunately, all my attempts were stuck on single problem.
There were error:
ERROR: In file '.docker-compose.yml', service 'environment' must be a mapping not an array.

Attempts:

  1. Flash SD Card using HypriotOS then:
    1.1. install kerberos-io as per : https://medium.com/@vpetersson/using-kerberos-io-with-docker-and-multiple-cameras-9eee66dcae31
    ##not succeed: ERROR: In file '.cam0.yml', service 'links' must be a mapping not an array.
    1.2. install kerberos-io as per : https://doc.kerberos.io/2.0/installation/Multi-camera/Docker
    ##not succeed: ERROR: In file '.docker-compose.yml', service 'links' must be a mapping not an array.
    1.3. install kerberos-io as per : https://doc.kerberos.io/2.0/installation/Docker
    ##not succeed: ERROR: In file '.docker-compose.yml', service 'environment' must be a mapping not an array.
  2. Flash SD Card using Raspbian Jessie Lite, install Docker, install Docker-compose then:
    2.1. install kerberos-io as per : https://medium.com/@vpetersson/using-kerberos-io-with-docker-and-multiple-cameras-9eee66dcae31
    ##not succeed: ERROR: In file '.cam0.yml', service 'links' must be a mapping not an array.
    2.2. install kerberos-io as per : https://doc.kerberos.io/2.0/installation/Docker
    ##not succeed: ERROR: In file '.docker-compose.yml', service 'environment' must be a mapping not an array.
  3. Install Docker on Windows7 then install kerberos-io as per https://doc.kerberos.io/2.0/installation/Docker
    ##not succeed: ERROR: In file '.docker-compose.yml', service 'environment' must be a mapping not an array.

Would you please show me what need to be corrected in order to run this kerberos-io on my Raspberry Pi? I am using the latest Raspbian Jessie Lite image releases and update it.
I ensured the Docker installation running well when it succeed running busybox image and hello-world.

Volumes not mapping properly

I am using the following, but the mappings do not work correctly...

docker run -d --name kerberos-camera1 -p 8859:80 -p 8860:8889 -v /cameras/config:/etc/opt/kerberosio/config -v /cameras/capture:/etc/opt/kerberosio/capture -v /cameras/logs:/etc/opt/kerberosio/logs kerberos/kerberos

...and while the web interface loads correctly, it returns...

Oops, something went wrong One or more config files are missing in /etc/opt/kerberosio/config.
Please check if the .xml files are available.

I tried the dockeros as suggested but could not figure the mappings out there either. I'd prefer to use the above command, can you tell me what the proper syntax is?

Persist login credentials

When using Docker the login credentials aren't persisted on a drive. Each time the docker container restarts, the new username and password are reset.

Have an option to disable internal cleanup

I've 4 cameras served by 4 instances of kerberos-docker (each writes into own sub-folder, i.e. /var/lib/kerberos.io/camX), and I noticed that some cameras have very less videos in the storage folder. I assume the reason is that I have 4 autoremoval instances running at the same time and depending on system load some may clean more files in its camera storage than others?
Is it possible to disable autoremoval code by, for example, checking for .noautoremoval file in this run.sh script?
Something like this:

[ -e /etc/opt/kerberosio/capture/.noautoremoval ] || autoremoval &

?
And then I'll write own script that will walk over all storages and do a clean-up, via cron or systemd timers.

web url not reachable

I am running

sudo docker run --name camera1 -p 90:80 -p 8889:8889 -d kerberos/kerberos

afterward both the livestream and the webgui are not reachable eventhough the docker container is running. What could be happening ?

image tags for each version

I was looking at the tag list for the docker containers and I was wondering if you plan on adding tags for the releases. Something like 2.8.0 in addition to having latest or master? That would support using a specific version and upgrading the version when desired as opposed to always pulling the latest, which could be newer versions I assume? Thanks!

Multi-architecture support

Context

We're creating a ARM Dockerfile, so Kerberos.io can also be used on other architectures as well. Afterwards we can use a manifest tool (http://container-solutions.com/multi-arch-docker-images/) to redirect to architecture specific images.

Registry

Currently the only way is to create separate tags to support different architectures (e.g. machinery-x86, machinery-armv7hf, machineryamd64, etc). This is not clean, therefore Docker is creating an OOTB implementation to support this feature. To be continued.

moby/moby/pull/27455

Manifest tool

We're using Docker's Edge feature docker manifest to map the different architectures.

Store images and video outside the docker container

This should be obvious but I couldn't find this in the documentation. I'm a Docker noob, so forgive me if this is a trivial question. By default the images captured are saved to /etc/opt/kerberosio/capture/, how do I save them to an drive outside the docker container?

Security issue: /stream is not secured

I'm using this docker image to run the service. I want to open the service to the internet but the /stream URI is not secured using any password.

location /stream {
		proxy_set_header Authorization $http_authorization;
		proxy_read_timeout 1s;
		proxy_pass http://localhost:8889;
}

I don't have a solution right now. The 'normal' authentication uses PHP, the /stream URI proxies straight to the other service. There is no PHP in between, so no authentication.

Latest Release

Hey! Is the Docker image version 2.5?

Setting up the image it appears to be running 2.4 with no available update.

Abnormal CPU load

Hey, I'm running Kerberos on docker on a Rpi3b. Usually it idles around 10-20%, apart from occasions when other processes are running. But it looks like every so often it goes above 40% and stays at that percentage until I restart the container.
image
image

the output image is automately removed??

Now i was running 4 docker container in virtual machine.
The kerbero.io is running very well. when some moved detected it save a image.
but after a few minute. That image was removed.

https://kerberosio.zendesk.com/hc/en-us/articles/202842272-Images-are-deleted-when-partition-is-almost-full

i was saw this answer. in this page you say if the disk is full the image will be removed automatically.
but this case is occured in kios.

this remove the image algorithm is same with docker?

XML-config-files not updated through web-interface

Hello,

I am using Version 2.8.0 on docker and just realised, that the XML-config-files (config folder is mapped to local volume) cannot be updated through the web-interface anymore. Obviously, this was once working, but somewhen along the update-path since V2.3.0, this glitch sneaked in.

I tried a new installation as well, but the issue remains. Any thoughts or directions?

Thank you,
Tom

Q-See QCN8001D - High CPU

Hello, i am running this on ESXi 7, Ubuntu 20.04 and docker within. single camera 1280x720 can go to 1080. getting high CPU on kerberosio 50%. can you tell me how to bring this down.

Can we set it to record all the time to save cpu?

my old nvr software just recorded, 6 cameras, it did not go over 20%

kerberosio - very high memory usage when 1024x768 resolution and delay set to 100

Memory usage is VERY high (eventually bringing my raspberry pi4 to a halt) when using specific configuration for raspberry onboard camera.

Steps to reproduce:

  1. Run: docker run --name camera -p 80:80 -p 8889:8889 -d -v /dev/vcsm:/dev/vcsm -v /dev/vchiq:/dev/vchiq --privileged kerberos/kerberos
  2. After initial configuration go to http://............./settings -> ADVANCED
  3. Change resolution to 1024x768
  4. Change delay to 100
  5. Make a continuous motion in front of the onboard camera ( I used a youtbe wideo with fractal zoom :) )

Result:
Within several minutes memory usage soars over 1.5GB, eventually raspberry pi runs out of memory, swap space kicks in and everything is halted.

Expected result:
Memory usage is expected to be reasonable :-)

Rig specs:

  • Hardware: Raspberry Pi 4 Model B Rev 1.1 (2GB)
  • OS: Raspbian GNU/Linux 10 (buster) with newest updates

image

image

IP/Port Config of Machinery

It would be nice if the Web Docker had a config variable for the Machinery IP and Port
Instead of using the hostname machinery and a static port 8889
this make using multiple docker container pairs very difficult, I had to bash into the container to override the hosts file and the port in the nginx config.

Deployment of kerberos/kerberos:latest fails

Hello folks,

I tried to deploy kerberos on my docker swarm the last days.

I run into the same issue someone had posted on kerberos/machinery:

2021-02-03 08:28:09,527 CRIT Set uid to user
2021-02-03 08:28:09,556 INFO RPC interface 'supervisor' initialized
2021-02-03 08:28:09,557 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2021-02-03 08:28:09,557 INFO supervisord started with pid 29
2021-02-03 08:28:10,562 INFO spawned: 'nginx' with pid 32
2021-02-03 08:28:10,567 INFO spawned: 'machinery' with pid 33
2021-02-03 08:28:10,796 INFO exited: machinery (exit status 255; not expected)
2021-02-03 08:28:11,798 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-03 08:28:11,801 INFO spawned: 'machinery' with pid 40
2021-02-03 08:28:11,982 INFO exited: machinery (exit status 255; not expected)
2021-02-03 08:28:13,990 INFO spawned: 'machinery' with pid 43
2021-02-03 08:28:14,196 INFO exited: machinery (exit status 255; not expected)
2021-02-03 08:28:17,203 INFO spawned: 'machinery' with pid 46
2021-02-03 08:28:17,403 INFO exited: machinery (exit status 255; not expected)
2021-02-03 08:28:18,405 INFO gave up: machinery entered FATAL state, too many start retries too quickly

also the web IF gives back a 502 bad gateway ofc.

Any hint on this ?

I tried to attach to the container but this times out.

Is it because the container is not privileged ? ( in Docker swarm env there are no priviledged containers... if i dont fork and recompile.... )

Why i use docker swarm:
Multiple endpoints ( raspi4 over WAN ) with cams ( in raspi4 local network ) and central storage/ management and routing.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.