Open 1vash opened 5 years ago
Hey Ivan.
Let's have a look at your config. I'm assuming you're trying to start a two container stack: One container for Shinobi and one for MariaDB, right? Ok, can you paste the content of your docker-compose.yml
, please? Remove any sensible information like passphrases, etc., please.
It looks like Shinobi is missing a supported password hash method. Please check if you provide the environment variable PASSWORD_HASH
to the Shinobi container. For new installations set PASSWORD_HASH=sha256
.
I recommend to pass the environment variables to set up the stack using environment files. This is an example of a simple two container stack setup:
version: '2'
services:
db:
image: mariadb
env_file:
- MySQL.env
volumes:
- ./microservice_datadir_debian:/var/lib/mysql
shinobi:
image: migoller/shinobidocker:microservice-debian-dev
env_file:
- MySQL.env
- Shinobi.env
volumes:
- /etc/localtime:/etc/localtime:ro
- /etc/timezone:/etc/timezone:ro
- ./config:/config
- ./videos:/opt/shinobi/videos
- /dev/shm/shinobiDockerTemp:/dev/shm/streams
ports:
- "8080:8080"
This is the sample content for MySQL.env
to setup the MariaDB server and to let Shinobi access the MariaDB server.
MYSQL_USER=majesticflame
MYSQL_PASSWORD=password
MYSQL_HOST=db
MYSQL_DATABASE=ccio
MYSQL_ROOT_PASSWORD=blubsblawoot
MYSQL_ROOT_USER=root
Ensure MYSQL_HOST
is set to the MariaDB container's name like db
.
Provide the environments variables for the Shinobi setup accordingly:
ADMIN_USER=admin@shinobi.video
ADMIN_PASSWORD=admin
CRON_KEY=YourCronKey
PLUGINKEY_MOTION=YourPluginMotionKey
PLUGINKEY_OPENCV=YourPluginOpenCvKey
PLUGINKEY_OPENALPR=YourPluginOpenAlprKey
MOTION_HOST=localhost
MOTION_PORT=8080
PASSWORD_HASH=sha256
The last line sets the required password hash method.
Good luck and please let me know if you can get it managed to start.
Regards, Michael
@MiGoller THe problem was in PASSWORD_HASH and after setting this environment variable all works well. I still have some questions:
P.S You can no answer these questions and I understand that maybe some of them has to be asked not here but maybe you can guide into right direction
Thanks a lot for your help Regards, Ivan
Hey Ivan,
sorry for coming back to you so lately. Had a lot of work at my profession.
I've tried to run some Shinobi plugins on docker but it's really hard to get GPU support working if you don't know what GPU your customers own, right? Well, if you're still interested in running the plugins on Docker, please have a look at my repos on GitLab: https://gitlab.com/MiGoller/shinobidockerplugins/-/tree/master . Let me know if you can go ahead with that template, please. It's outdated on Node JS 8 but I'll have a look at it to port it to my new baseline.
From my point of view Docker is able to support GPU from AMD, Intel and nVidia on AMD64 architecture. Cause I have no CUDA-enabled device I do not provide any Shinobi Docker images for nVidia. You man want to give my current ArchLinux build a try and the new upcoming microservice image based on phusion baseimage including baasic VDPAU and VAAPI support and a curremt ffmpeg release with hw-accell support.
If you have any questions regarding the plugins or the Shinobi App itself please join us on Discord. You'll find the most recent invitation link on the Shinobi homepage.
Thank you for your patience.
Best Regards,
Michael
Btw. This is aws fresh guided installation Dock the "microservice" Shinobi Docker image from your page step by step https://gitlab.com/MiGoller/ShinobiDocker
Trully cannot understand what should I do to make it work. Help please. I even changed all default passwords but couldn't succeed.
uname -a