- Hash super admin password (undefined)...

[1vash]

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

Linux ip-172-31-44-76 4.15.0-1044-aws #46-Ubuntu SMP Thu Jul 4 13:38:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

((root@ip-172-31-44-76:/home/ShinobiDocker# docker-compose up
Starting shinobidocker_shinobi_1 ... 
shinobidocker_db_1 is up-to-date
Starting shinobidocker_shinobi_1 ... done
Attaching to shinobidocker_db_1, shinobidocker_shinobi_1
shinobi_1  | Copy custom configuration files ...
shinobi_1  | Waiting for connection to MariaDB server on db .mysqladmin: connect to server at 'db' failed
shinobi_1  | error: 'Access denied for user 'root'@'172.18.0.3' (using password: NO)'
shinobi_1  |  established.
shinobi_1  | Setting up MariaDB database if it does not exists ...
db_1       | Initializing database
db_1       | 
db_1       | 
db_1       | PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
db_1       | To do so, start the server, then issue the following commands:
db_1       | 
db_1       | '/usr/bin/mysqladmin' -u root password 'new-password'
db_1       | '/usr/bin/mysqladmin' -u root -h  password 'new-password'
db_1       | 
db_1       | Alternatively you can run:
db_1       | '/usr/bin/mysql_secure_installation'
db_1       | 
db_1       | which will also give you the option of removing the test
db_1       | databases and anonymous user created by default.  This is
db_1       | strongly recommended for production servers.
db_1       | 
db_1       | See the MariaDB Knowledgebase at http://mariadb.com/kb or the
db_1       | MySQL manual for more instructions.
db_1       | 
db_1       | Please report any problems at http://mariadb.org/jira
db_1       | 
db_1       | The latest information about MariaDB is available at http://mariadb.org/.
db_1       | You can find additional information about the MySQL part at:
db_1       | http://dev.mysql.com
db_1       | Consider joining MariaDB's strong and vibrant community:
db_1       | https://mariadb.org/get-involved/
db_1       | 
db_1       | Database initialized
db_1       | MySQL init process in progress...
db_1       | 2019-07-22 15:58:20 0 [Note] mysqld (mysqld 10.4.6-MariaDB-1:10.4.6+maria~bionic) starting as process 107 ...
db_1       | 2019-07-22 15:58:20 0 [Note] InnoDB: Using Linux native AIO
db_1       | 2019-07-22 15:58:20 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
db_1       | 2019-07-22 15:58:20 0 [Note] InnoDB: Uses event mutexes
db_1       | 2019-07-22 15:58:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
db_1       | 2019-07-22 15:58:20 0 [Note] InnoDB: Number of pools: 1
db_1       | 2019-07-22 15:58:20 0 [Note] InnoDB: Using SSE2 crc32 instructions
db_1       | 2019-07-22 15:58:20 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
db_1       | 2019-07-22 15:58:20 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
db_1       | 2019-07-22 15:58:20 0 [Note] InnoDB: Completed initialization of buffer pool
db_1       | 2019-07-22 15:58:20 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
db_1       | 2019-07-22 15:58:21 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
db_1       | 2019-07-22 15:58:21 0 [Note] InnoDB: Creating shared tablespace for temporary tables
db_1       | 2019-07-22 15:58:21 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
db_1       | 2019-07-22 15:58:21 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
db_1       | 2019-07-22 15:58:21 0 [Note] InnoDB: Waiting for purge to start
db_1       | 2019-07-22 15:58:21 0 [Note] InnoDB: 10.4.6 started; log sequence number 139827; transaction id 21
db_1       | 2019-07-22 15:58:21 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
db_1       | 2019-07-22 15:58:21 0 [Note] Plugin 'FEEDBACK' is disabled.
db_1       | 2019-07-22 15:58:21 0 [Warning] 'user' entry 'root@6084ad4d5b1a' ignored in --skip-name-resolve mode.
db_1       | 2019-07-22 15:58:21 0 [Warning] 'user' entry '@6084ad4d5b1a' ignored in --skip-name-resolve mode.
db_1       | 2019-07-22 15:58:21 0 [Warning] 'proxies_priv' entry '@% root@6084ad4d5b1a' ignored in --skip-name-resolve mode.
db_1       | 2019-07-22 15:58:21 0 [Note] Reading of all Master_info entries succeeded
db_1       | 2019-07-22 15:58:21 0 [Note] Added new Master_info '' to hash table
db_1       | 2019-07-22 15:58:21 0 [Note] mysqld: ready for connections.
db_1       | Version: '10.4.6-MariaDB-1:10.4.6+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
db_1       | 2019-07-22 15:58:21 0 [Note] InnoDB: Buffer pool(s) load completed at 190722 15:58:21
db_1       | Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
db_1       | 2019-07-22 15:58:45 10 [Warning] 'proxies_priv' entry '@% root@6084ad4d5b1a' ignored in --skip-name-resolve mode.
db_1       | 
db_1       | 2019-07-22 15:58:45 0 [Note] mysqld (initiated by: unknown): Normal shutdown
db_1       | 2019-07-22 15:58:45 0 [Note] Event Scheduler: Purging the queue. 0 events
db_1       | 2019-07-22 15:58:45 0 [Note] InnoDB: FTS optimize thread exiting.
db_1       | 2019-07-22 15:58:45 0 [Note] InnoDB: Starting shutdown...
db_1       | 2019-07-22 15:58:45 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
db_1       | 2019-07-22 15:58:45 0 [Note] InnoDB: Buffer pool(s) dump completed at 190722 15:58:45
db_1       | 2019-07-22 15:58:46 0 [Note] InnoDB: Shutdown completed; log sequence number 139836; transaction id 24
db_1       | 2019-07-22 15:58:46 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
db_1       | 2019-07-22 15:58:46 0 [Note] mysqld: Shutdown complete
db_1       | 
db_1       | 
db_1       | MySQL init process done. Ready for start up.
db_1       | 
db_1       | 2019-07-22 15:58:46 0 [Note] mysqld (mysqld 10.4.6-MariaDB-1:10.4.6+maria~bionic) starting as process 1 ...
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Using Linux native AIO
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Uses event mutexes
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Number of pools: 1
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Using SSE2 crc32 instructions
db_1       | 2019-07-22 15:58:47 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Completed initialization of buffer pool
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Creating shared tablespace for temporary tables
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Waiting for purge to start
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: 10.4.6 started; log sequence number 139836; transaction id 21
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
db_1       | 2019-07-22 15:58:47 0 [Note] Plugin 'FEEDBACK' is disabled.
db_1       | 2019-07-22 15:58:47 0 [Note] Server socket created on IP: '::'.
db_1       | 2019-07-22 15:58:47 0 [Warning] 'proxies_priv' entry '@% root@6084ad4d5b1a' ignored in --skip-name-resolve mode.
db_1       | 2019-07-22 15:58:47 0 [Note] Reading of all Master_info entries succeeded
db_1       | 2019-07-22 15:58:47 0 [Note] Added new Master_info '' to hash table
db_1       | 2019-07-22 15:58:47 0 [Note] InnoDB: Buffer pool(s) load completed at 190722 15:58:47
db_1       | 2019-07-22 15:58:47 0 [Note] mysqld: ready for connections.
db_1       | Version: '10.4.6-MariaDB-1:10.4.6+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
db_1       | 2019-07-22 15:58:48 8 [Warning] Access denied for user 'root'@'172.18.0.3' (using password: NO)
db_1       | 2019-07-22 15:58:48 9 [Warning] Access denied for user 'rot'@'172.18.0.3' (using password: YES)
db_1       | 2019-07-22 15:58:48 10 [Warning] Access denied for user 'rot'@'172.18.0.3' (using password: YES)
db_1       | 2019-07-22 15:58:48 11 [Warning] Access denied for user 'rot'@'172.18.0.3' (using password: YES)
db_1       | 2019-07-22 15:59:25 12 [Warning] Access denied for user 'root'@'172.18.0.3' (using password: NO)
shinobi_1  |  - Set database name: ccio
shinobi_1  | - Create database schema if it does not exists ...
shinobi_1  | ERROR 1045 (28000): Access denied for user 'rot'@'172.18.0.3' (using password: YES)
shinobi_1  | - Fix user table for LDAP auth issues ...
db_1       | 2019-07-22 15:59:25 13 [Warning] Access denied for user 'rot'@'172.18.0.3' (using password: YES)
shinobi_1  | ERROR 1045 (28000): Access denied for user 'rot'@'172.18.0.3' (using password: YES)
db_1       | 2019-07-22 15:59:25 14 [Warning] Access denied for user 'rot'@'172.18.0.3' (using password: YES)
shinobi_1  | - Create database user if it does not exists ...
shinobi_1  | ERROR 1045 (28000): Access denied for user 'rot'@'172.18.0.3' (using password: YES)
db_1       | 2019-07-22 15:59:25 15 [Warning] Access denied for user 'rot'@'172.18.0.3' (using password: YES)
shinobi_1  | Updating Shinobi's configuration to match your environment ...
shinobi_1  | - Set MariaDB configuration from environment variables ...
shinobi_1  |   - MariaDB username: majesticflamee
shinobi_1  | db.user: majesticflamee
shinobi_1  |   - MariaDB password.
shinobi_1  | db.password: pswd
shinobi_1  |   - MariaDB server host: db
shinobi_1  | db.host: db
shinobi_1  |   - MariaDB database name: ccio
shinobi_1  | db.database: ccio
shinobi_1  | - Set keys for CRON and PLUGINS from environment variables ...
shinobi_1  | cron.key: b59b5c62-57d0-4cd1-b068-a55e5222786f
shinobi_1  | pluginKeys.Motion: 49ad732d-1a4f-4931-8ab8-d74ff56dac57
shinobi_1  | pluginKeys.OpenCV: 6aa3487d-c613-457e-bba2-1deca10b7f5d
shinobi_1  | pluginKeys.OpenALPR: 59859194-847chbv
shinobi_1  | Set configuration for motion plugin from environment variables ...
shinobi_1  | host: localhost
shinobi_1  | port: 8080
shinobi_1  | key: 49ad732d-1a4f-4931-8ab8-d74ff56dac57
shinobi_1  | - Set the super admin credentials ...
shinobi_1  |   - Hash super admin password (undefined)...
shinobi_1  | Unsupported password type undefined. Set to md5, sha256 or sha512.
shinobidocker_shinobi_1 exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
Stopping shinobidocker_db_1 ... done
root@ip-172-31-44-76:/home/ShinobiDocker# ^C
root@ip-172-31-44-76:/home/ShinobiDocker# docker-compose -f ./docker-compose.yml create
WARNING: The create command is deprecated. Use the up command with the --no-start flag instead.
root@ip-172-31-44-76:/home/ShinobiDocker# ^Ccker-compose -f ./docker-compose.yml create
root@ip-172-31-44-76:/home/ShinobiDocker# ^C
root@ip-172-31-44-76:/home/ShinobiDocker# docker-compose -f ./docker-compose.yml up
Starting shinobidocker_shinobi_1 ... 
Starting shinobidocker_db_1 ... 
Starting shinobidocker_shinobi_1
Starting shinobidocker_db_1 ... done
Attaching to shinobidocker_shinobi_1, shinobidocker_db_1
shinobi_1  | Copy custom configuration files ...
shinobi_1  | Waiting for connection to MariaDB server on db .mysqladmin: connect to server at 'db' failed
shinobi_1  | error: 'Can't connect to MySQL server on 'db' (111 "Connection refused")'
shinobi_1  | Check that mysqld is running on db and that the port is 3306.
shinobi_1  | You can check this by doing 'telnet db 3306'
db_1       | 2019-07-22 16:00:31 0 [Note] mysqld (mysqld 10.4.6-MariaDB-1:10.4.6+maria~bionic) starting as process 1 ...
db_1       | 2019-07-22 16:00:31 0 [Note] InnoDB: Using Linux native AIO
db_1       | 2019-07-22 16:00:31 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
db_1       | 2019-07-22 16:00:31 0 [Note] InnoDB: Uses event mutexes
db_1       | 2019-07-22 16:00:31 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
db_1       | 2019-07-22 16:00:31 0 [Note] InnoDB: Number of pools: 1
db_1       | 2019-07-22 16:00:31 0 [Note] InnoDB: Using SSE2 crc32 instructions
db_1       | 2019-07-22 16:00:31 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
db_1       | 2019-07-22 16:00:31 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
db_1       | 2019-07-22 16:00:31 0 [Note] InnoDB: Completed initialization of buffer pool
db_1       | 2019-07-22 16:00:31 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
db_1       | 2019-07-22 16:00:32 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
db_1       | 2019-07-22 16:00:32 0 [Note] InnoDB: Creating shared tablespace for temporary tables
db_1       | 2019-07-22 16:00:32 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
db_1       | 2019-07-22 16:00:32 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
db_1       | 2019-07-22 16:00:32 0 [Note] InnoDB: Waiting for purge to start
db_1       | 2019-07-22 16:00:32 0 [Note] InnoDB: 10.4.6 started; log sequence number 139845; transaction id 21
db_1       | 2019-07-22 16:00:32 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
db_1       | 2019-07-22 16:00:32 0 [Note] Plugin 'FEEDBACK' is disabled.
db_1       | 2019-07-22 16:00:32 0 [Note] Server socket created on IP: '::'.
db_1       | 2019-07-22 16:00:32 0 [Warning] 'proxies_priv' entry '@% root@6084ad4d5b1a' ignored in --skip-name-resolve mode.
db_1       | 2019-07-22 16:00:32 0 [Note] Reading of all Master_info entries succeeded
db_1       | 2019-07-22 16:00:32 0 [Note] Added new Master_info '' to hash table
db_1       | 2019-07-22 16:00:32 0 [Note] mysqld: ready for connections.
db_1       | Version: '10.4.6-MariaDB-1:10.4.6+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
db_1       | 2019-07-22 16:00:32 0 [Note] InnoDB: Buffer pool(s) load completed at 190722 16:00:32
db_1       | 2019-07-22 16:00:32 8 [Warning] Access denied for user 'root'@'172.18.0.2' (using password: NO)
shinobi_1  | .mysqladmin: connect to server at 'db' failed
shinobi_1  | error: 'Access denied for user 'root'@'172.18.0.2' (using password: NO)'
shinobi_1  |  established.
shinobi_1  | Setting up MariaDB database if it does not exists ...
shinobi_1  |  - Set database name: ccio
shinobi_1  | - Create database schema if it does not exists ...
db_1       | 2019-07-22 16:00:32 9 [Warning] Access denied for user 'rot'@'172.18.0.2' (using password: YES)
shinobi_1  | ERROR 1045 (28000): Access denied for user 'rot'@'172.18.0.2' (using password: YES)
shinobi_1  | - Fix user table for LDAP auth issues ...
db_1       | 2019-07-22 16:00:32 10 [Warning] Access denied for user 'rot'@'172.18.0.2' (using password: YES)
shinobi_1  | ERROR 1045 (28000): Access denied for user 'rot'@'172.18.0.2' (using password: YES)
shinobi_1  | - Create database user if it does not exists ...
db_1       | 2019-07-22 16:00:32 11 [Warning] Access denied for user 'rot'@'172.18.0.2' (using password: YES)
shinobi_1  | ERROR 1045 (28000): Access denied for user 'rot'@'172.18.0.2' (using password: YES)
shinobi_1  | Updating Shinobi's configuration to match your environment ...
shinobi_1  | - Set MariaDB configuration from environment variables ...
shinobi_1  |   - MariaDB username: majesticflamee
shinobi_1  | db.user: majesticflamee
shinobi_1  |   - MariaDB password.
shinobi_1  | db.password: pswd
shinobi_1  |   - MariaDB server host: db
shinobi_1  | db.host: db
shinobi_1  |   - MariaDB database name: ccio
shinobi_1  | db.database: ccio
shinobi_1  | - Set keys for CRON and PLUGINS from environment variables ...
shinobi_1  | cron.key: b59b5c62-57d0-4cd1-b068-a55e5222786f
shinobi_1  | pluginKeys.Motion: 49ad732d-1a4f-4931-8ab8-d74ff56dac57
shinobi_1  | pluginKeys.OpenCV: 6aa3487d-c613-457e-bba2-1deca10b7f5d
shinobi_1  | pluginKeys.OpenALPR: 59859194-847chbv
shinobi_1  | Set configuration for motion plugin from environment variables ...
shinobi_1  | host: localhost
shinobi_1  | port: 8080
shinobi_1  | key: 49ad732d-1a4f-4931-8ab8-d74ff56dac57
shinobi_1  | - Set the super admin credentials ...
shinobi_1  |   - Hash super admin password (undefined)...
shinobi_1  | Unsupported password type undefined. Set to md5, sha256 or sha512.
shinobidocker_shinobi_1 exited with code 1)
)

[MiGoller]

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

[1vash]

@MiGoller THe problem was in PASSWORD_HASH and after setting this environment variable all works well.
I still have some questions:

1. What should I do to add plugins to docker? I'm interested in object detection plugins ( via OpenCV and Yolo ) as well as my own written ones
2. Right now I don't see any docker GPU support am I right that it's not developed yet? I Couldn't see any nvidia-docker support and as I know the only way to add GPU support is by using nvidia-docker
3. what should I do with yolo/opencv detectors to see any green boxes during video? I use GPU shinobi modules/plugins support
   Even nvidia-smi shows | 0 1492 C ...hinobi/plugins/opencv/shinobi-opencv.js 61MiB |
   maybe I installed something wrong or anything else. Monitor Setting shows Object Detection Yolo, OpenCV Connected and Send Frames as well as Save Events to SQL is on Yes
   Nothing more in goggle I haven't found what to do to see video flow with green boxes

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

[MiGoller]

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