jshridha / docker-blueiris Goto Github PK

Hi and thanks for the great docker! Initially I could not get BI install to launch. I did manage to get it up and running by:

docker exec -it BlueIris /bin/bash
wget http://blueirissoftware.com/blueiris.exe
./blueiris.sh

I initially tried just running the blueiris.sh file but it complained that the blueiris.exe didn't exist so I grabbed it with wget and then launched the script and things started working.

I'm not sure where the problem is with the script but I'm guessing it is just not downloading the software and that causes things to break.

Everything seems to be working except for web access. I got this error when trying to use authentication:

https://i.imgur.com/Pju78Y8.png

I installed UI3 and was able to get in fine but only if I keep authentication off which is not ideal. Any ideas on what could be causing this problem?

Why is this docker container using WINE to run BI when microsoft publishes windows docker images? Just install BI in the windows docker container and enable RDP.

Is this possible?

-- Reese

Here's where my docker-compose is at, at the moment:

version: '3'

services:
  blue-iris:
    image: leonowski/docker-blueiris:pull_request
    restart: unless-stopped
    privileged: true
    environment:
    - RESOLUTION=1440x768x24
    ports:
    - 8080:8080
    - 5900:5900
    - 81:81
    volumes:
    - ~/blue-iris/system.reg:/root/prefix/system.reg:rw
    - ~/blue-iris/userdef.reg:/root/prefix/userdef.reg:rw
    - ~/blue-iris/user.reg:/root/prefix/user.reg:rw
    - /SURVEILLANCE/blue-iris:/root/prefix/drive_c/BlueIris

Volume mounting just the couple .reg files seems to work well to get the settings into new containers, but when modifying the settings through the Blue Iris UI, they don't seem to end up back on the host machine. I'm not sure why this is.

Volume mounting the "New" and "Stored" folders gets the recordings onto the host machine, but later they magically disappear. Which has me a little baffled. Edit: I think maybe this is fixed.

Looking for advice/ideas on how to proceed.

@leonowski Any ideas?

Installing this under unRAID. Have gotten as far as installing the Docker, loading VNC. It installs the two initial WINE packages (wine-mono and Gecko), but when it moves on to "Extracting main application files..." it results in an "Invalid Command Line" error. Clicking OK, just send it into a loop of attempting the main app files again.

I know I'm probably missing something here - I'm a total Docker noob. Any suggestions would be appreciated, thanks!

Log attached:

/usr/lib/python2.7/dist-packages/supervisor/options.py:297: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2019-09-04 13:02:35,953 CRIT Supervisor running as root (no user in config file)
2019-09-04 13:02:35,953 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2019-09-04 13:02:35,963 INFO RPC interface 'supervisor' initialized
2019-09-04 13:02:35,963 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-09-04 13:02:35,963 INFO supervisord started with pid 1
2019-09-04 13:02:36,965 INFO spawned: 'x11vnc' with pid 8
2019-09-04 13:02:36,966 INFO spawned: 'X11' with pid 9
2019-09-04 13:02:36,967 INFO spawned: 'progman' with pid 10
2019-09-04 13:02:36,969 INFO spawned: 'x11vnc-loc' with pid 11
2019-09-04 13:02:36,971 INFO spawned: 'novnc' with pid 12
2019-09-04 13:02:37,983 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-09-04 13:02:37,983 INFO success: X11 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-09-04 13:02:37,983 INFO success: progman entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-09-04 13:02:37,983 INFO success: x11vnc-loc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-09-04 13:02:37,983 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-09-04 13:02:46,139 INFO reaped unknown pid 54
2019-09-04 13:03:09,154 INFO reaped unknown pid 91
2019-09-04 13:03:11,244 INFO reaped unknown pid 86
2019-09-04 13:03:31,688 INFO reaped unknown pid 93
2019-09-04 13:03:31,896 INFO reaped unknown pid 122
2019-09-04 13:03:32,022 INFO reaped unknown pid 80
2019-09-04 13:03:34,029 INFO reaped unknown pid 52
2019-09-04 13:04:47,305 INFO exited: progman (exit status 2; expected)
2019-09-04 13:04:48,302 INFO spawned: 'progman' with pid 163
2019-09-04 13:04:48,303 INFO reaped unknown pid 76
2019-09-04 13:04:48,302 INFO spawned: 'progman' with pid 163
2019-09-04 13:04:48,303 INFO reaped unknown pid 76
2019-09-04 13:04:49,317 INFO success: progman entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-09-04 13:04:51,307 INFO reaped unknown pid 135
2019-09-04 13:04:51,310 INFO reaped unknown pid 59
2019-09-04 13:04:51,326 INFO reaped unknown pid 67
2019-09-04 13:04:51,326 INFO reaped unknown pid 72
2019-09-04 13:04:51,327 INFO reaped unknown pid 141
2019-09-04 13:04:51,328 INFO reaped unknown pid 56
2019-09-04 13:04:51,330 INFO reaped unknown pid 50
2019-09-04 13:04:56,736 INFO reaped unknown pid 182
2019-09-04 13:04:57,228 INFO reaped unknown pid 184
2019-09-04 13:04:57,228 INFO reaped unknown pid 184

Good morning,

I've been utilizing blueiris in a docker for the past few months, throughout this time my timeline has been incorrect in blueiris. It is 6 hours ahead exactly, therefore I have been utilizing the camera overlay on the image so the camera streams display the proper time, although I would prefer to use blueiris for the overlay.

I would also love to have the timeline displaying the correct time, so I've been digging in to this a bit lately.

I initially ran the master branch, followed by the dev branch, and now the gpu branch. I've only switched to the dev and gpu branches as I saw the creator of this claim the time issues were fixed in these versions quite some time ago.

I have the following variables passed in my buildfile in an attempt to correct the time.
-e TZ=America/Chicago
-v /etc/localtime:/etc/localtime:ro
-v /etc/timezone:/etc/timezone:ro
... None of these work or I wouldn't be here.

I have also tried the following wine registry edit
docker exec -it <container_name> /bin/bash
wine reg add 'HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation' /v TimeZoneKeyName /t REG_SZ /d 'Central Standard Time' /f

Also checking the time and timezone in the docker using any time commands I've been able to find, all display that the time is set to CST or America/Chicago

I'd really love to get this resolved, if anyone could let me know how they have resolved this, or if people are just dealing with it...

getting this error when running ./blueiris.sh

0043:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.

Anyway to get this "ntlm_auth >= 3.0.25" updated in the next build?

Hi. This is not an issue but a few questions before I give this a try. I'm in the process of building an Open Media Vault NAS which can run docker containers. My goal is to consolidate a bunch of different servers/apps that I've got running on various windows and linux boxes. The machine I'm putting together is a HP workstation z210 tower, i5 2500 3.3.GHz, 4gb RAM . I'll probably end up increasing the RAM sooner than later.

One of the apps I'd like to move to the OMV server is Blue Iris. Here's my questions regarding your docker container:

• Can you tell me how well this is performing for you? I've got four wifi cameras. I'm also using alerts for motion to act as motion detectors for those areas with my home automation software (Home Assistant)
• How are BI software upgrades handled?
• How is the stability?

Thanks for sharing this. I'm hoping to give this a try once I get everything up and running with the NAS.

#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@                                                           @#
#@  **  WARNING  **  WARNING  **  WARNING  **  WARNING  **   @#
#@                                                           @#
#@        YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!!        @#
#@                                                           @#
#@  This means anyone with network access to this computer   @#
#@  may be able to view and control your desktop.            @#
#@                                                           @#
#@ >>> If you did not mean to do this Press CTRL-C now!! <<< @#
#@                                                           @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#

Seems like since ui3 is locked down with auth, maybe the desktop app should be too.

I am mounting my ssd on /root/prefix32 as the README states, but when I do that, the vnc interface is blank (it manages to connect though).

If I do not mount anything, then the vnc (eventually) shows wine getting configured and eventually BlueIris.

Any idea what's going on? This is the blkid for that drive:

UUID="84D5-0848" BLOCK_SIZE="512" TYPE="exfat" PTTYPE="dos"

Hi, my blueiris keeps crashing due to a read access error. Below is the backtrace. It's only recently started doing this, and happens completely randomly. I've double checked that all directories have the correct permissions.

backtrace.txt

Upon startup or restart, www does not have login.htm:

ls /root/prefix32/drive_c/Program\ Files/Blue\ Iris\ 5/www/
applet  clappr  livestream.htm  timeout.htm  ui3  ui3.htm  xlogin.htm

When navigating to http://[your machine's ip here]:81/login.htm?page=%2F a 404 is returned, further confirming that this .htm file is missing.

A short-term workaround is to

rm -rf /root/prefix32/drive_c/Program\ Files/Blue\ Iris\ 5/www/* && unzip /root/prefix32/drive_c/Program\ Files/Blue\ Iris\ 5/ui3.zip -d /root/prefix32/drive_c/Program\ Files/Blue\ Iris\ 5/www/

Referenced here: #13

However this workaround is only good until the container is restarted, at which point the workaround will need run again; making this not a viable solution.

I cannot for the life of me figure out how to set time on this container.

I've tried passing TZ=America/Chicago as an environment variable when running the container.

I've tried linking /etc/timezone to /usr/share/zoneinfo/America/Chicago .

The date appears to be correct if I do an exec bash on the container but despite all this, my timestamps show up as UTC.

Can someone tell me how to set time? Thanks

I've been trying to get this to run for a couple of days now. Sorry if this is obvious and thx for making this available.

I start the container, get 2-3 wine mono/gecko installers. Then BI5 install starts. Installs the Microsoft components. Then installs the BI5 application.

So far so good. But when I run BI5 - either using the checkbox after install while still in privileged mode, or by restarting the container - i get the following repeating errors:

0033:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0033:err:module:import_dll Library VCRUNTIME140_1.dll (which is needed by L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe") not found
07/09/2020 15:15:48 copy_tiles: allocating first_line at size 61
0033:err:module:import_dll Library mfc140u.dll (which is needed by L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe") not found
0033:err:module:import_dll Library FTD2XX.dll (which is needed by L"C:\\Program Files\\Blue Iris 5\\SeaMAX.dll") not found
0033:err:module:import_dll Library SeaMAX.dll (which is needed by L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe") not found
0033:err:module:LdrInitializeThunk Importing dlls for L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe" failed, status c0000135
2020-09-07 15:15:48,065 INFO exited: blueiris (exit status 53; not expected)
2020-09-07 15:15:50,068 INFO spawned: 'blueiris' with pid 133
0037:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0037:err:module:import_dll Library VCRUNTIME140_1.dll (which is needed by L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe") not found
0037:err:module:import_dll Library mfc140u.dll (which is needed by L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe") not found
0037:err:module:import_dll Library FTD2XX.dll (which is needed by L"C:\\Program Files\\Blue Iris 5\\SeaMAX.dll") not found
0037:err:module:import_dll Library SeaMAX.dll (which is needed by L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe") not found
0037:err:module:LdrInitializeThunk Importing dlls for L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe" failed, status c0000135
2020-09-07 15:15:50,570 INFO exited: blueiris (exit status 53; not expected)
2020-09-07 15:15:53,574 INFO spawned: 'blueiris' with pid 141

Not sure if this is winetricks related.

This is with a fresh wine prefix (empty /root/prefix mapped to a local drive)

docker run cmd:
docker run -d --name='blueiris' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'RESOLUTION'='1920x960x24' -p '8123:8080/tcp' -p '8987:81/tcp' -v '/mnt/user/appdata/bi5-docker/':'/root/prefix':'rw' --log-opt max-size=5m --log-opt max-file=2 'jh/bi5:jshridha'

** rebuilt the image only to add the blueiris.exe installer so I didn't have to keep redownloading it

This is on the dev branch

Any ideas?

Hello! Great work I was wondering if you could make a version with the Blue Iris 4 version.

Here is exe link: https://blueirissoftware.com/BlueIris_48603.exe

I just started trying to dev on this container again and give it some updates. I started with the dev branch and noticed that the detect/identify feature in BlueIris no longer works. It stalls out when trying to make a GET request on the local network. Switching back to the master branch works without issue.

@leonowski @TonyBrobston Do you know where in the changes you made could have caused this? Perhaps in the change from running as non-root user or in the run as service changes?

I recently decided to make some changes to my Blue Iris setup.

I'm running on the run_as_service branch.

Awhile back I made some file permission changes to my Blue Iris folder on my host machine. This caused problems (as you could probably imagine). I started seeing this error:

After some digging I found a previous conversation where we chmod -R 777 and chown 1000:1000 on /SURVEILLANCE/blue-iris in my case. I ran these commands and everything seemed to be looking good again.

At some point I restarted my container and started getting the same error as above and it seems that no matter what I try I can't get past it.

It seems as though the service is still running the background because ui3 is still letting me see my cameras and recording with node-deepstackai-trigger is still working, I just can't get to the regular BlueIris Windows application to make changes.

@leonowski any ideas what this might be?

Another separate issue, I tried a fresh install and am seeing two issues I also can't get past.

1. When I try to enter my license key there is a "Program Error" it gives me an option to "Show Details" but nothing every loads.
   

Here is what I see in the logs when I click "Close"; seems to be a stackoverflow at the end:

Process of pid=00e4 has terminated
No process loaded, cannot execute 'echo Modules:'
Cannot get info on module while no process is loaded
No process loaded, cannot execute 'echo Threads:'
process  tid      prio (all id:s are in hex)
00000038 services.exe
  0000003c    0
  00000040    0
  00000054    0
  00000074    0
  00000094    0
  000000c8    0
  000000d0    0
0234:fixme:variant:get_date_format ignoring flags 402
00000044 winedevice.exe
  00000048    0
  0000005c    0
  00000060    0
0000004c explorer.exe
  00000050    0
  00000070    0
  0000008c    0
00000068 plugplay.exe
  0000006c    0
  00000078    0
  0000007c    0
  00000080    0
  000000a8    0
00000084 winedevice.exe
  00000088    0
  0000009c    0
  000000a0    0
  000000a4    0
  000000b0    0
  000000b4    0
000000b8 BlueIris.exe
  000000bc    0
  000000cc    0
  000000d4    0
  000000d8    0
  000000f4    0
  000000f8    0
  000000fc    0
  00000100    0
  00000104    0
  00000108    0
  0000010c    0
  00000110    0
  00000114    0
  00000118    0
  0000011c    0
  00000120    0
  00000124    0
  00000128    0
  0000012c    0
  00000130    0
  00000134    0
  00000138    0
  0000013c    0
  00000140    0
  00000144    0
  00000148    0
  0000014c    0
  00000150    0
  00000154    0
  00000158    0
  0000015c    0
  00000160    0
  00000164    0
  00000168    0
  0000016c    0
  00000170    0
  00000174    0
  00000178    0
  0000017c    0
  00000180    0
  00000184    0
  00000188    0
  0000018c    0
  00000190    0
  00000194    0
  00000198    0
  0000019c    0
  000001a0    0
  000001a4    0
  000001a8    0
  000001ac    0
  000001b0    0
  000001b4    0
  000001b8    0
  000001bc    0
  000001c0    0
  000001c4    0
  000001c8    0
  000001cc    0
  000001d0    0
  000001d4    0
  000001d8    0
  000001dc    0
  000001e0    0
  000001e4    0
  000001e8    0
  000001ec    0
  000001f0    0
  000001fc    0
  00000200    0
  00000204    0
  00000208    0
  0000020c    0
  00000210   -1
  00000214    0
  00000218    0
  0000021c    0
  0000022c    0
  00000230    0
  00000234    1
  00000238    0
  0000023c    0
  00000240    0
  00000244    0
  00000248    0
  0000024c    0
  00000250    0
0278:err:virtual:virtual_setup_exception stack overflow 2864 bytes in thread 0278 addr 0x7bc5a322 stack 0x1204d0 (0x120000-0x121000-0x220000)

2. If I enter demo mode and "Check for News and Updates", I don't seem to have an internet connection. I think this is a symptom of a bigger issue.
   

Not sure if this is OK to include in the official image, but I have a way to automate the Demo button of the Evaluation window on startup.

I wanted to have a fully automated service with VAAPI features (apparently can't run as a service and have VAAPI) without entering my license info yet. I'll wait until it's all set up and I'm done creating and destroying the container.

The trick uses the already included xdotool to run a mouse macro and click the Demo button on startup, initiated by supervisord

Add the following to the end of the supervisord config file: /etc/supervisor/conf.d/supervisord-normal.conf

[program:demo-xdotool]
command=bash -c "sleep 5 && xdotool mousemove -polar 0 0 && xdotool mousemove_relative -- 280 255 && xdotool click --window `xdotool getactivewindow` 1"
autorestart=false
user=root

OS: Unraid 6.8.3
CPU: Intel 5960x
Memory: 64 GB
Host: unraid dock

After install on Blue Iris in the container the application never starts up. I tried many time and no go. Below is what I see in the docker logs. I have pages and pages of the same thing. Any help would be great.

2021-02-17 13:36:06,738 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:08,741 INFO spawned: 'blueiris' with pid 8184
2021-02-17 13:36:10,406 INFO success: blueiris entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-17 13:36:10,406 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:11,408 INFO spawned: 'blueiris' with pid 8190
2021-02-17 13:36:12,134 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:13,136 INFO spawned: 'blueiris' with pid 8196
2021-02-17 13:36:13,846 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:15,850 INFO spawned: 'blueiris' with pid 8202
2021-02-17 13:36:17,569 INFO success: blueiris entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-17 13:36:17,569 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:18,571 INFO spawned: 'blueiris' with pid 8208
2021-02-17 13:36:20,257 INFO success: blueiris entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-17 13:36:20,257 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:21,260 INFO spawned: 'blueiris' with pid 8214
2021-02-17 13:36:21,947 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:22,948 INFO spawned: 'blueiris' with pid 8220
2021-02-17 13:36:23,701 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:25,704 INFO spawned: 'blueiris' with pid 8226
2021-02-17 13:36:26,349 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:29,353 INFO spawned: 'blueiris' with pid 8236
2021-02-17 13:36:30,619 INFO success: blueiris entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-17 13:36:31,454 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:31,455 INFO spawned: 'blueiris' with pid 8280
2021-02-17 13:36:33,114 INFO success: blueiris entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-17 13:36:33,114 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:34,116 INFO spawned: 'blueiris' with pid 8286
2021-02-17 13:36:35,851 INFO success: blueiris entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-17 13:36:35,851 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:36,853 INFO spawned: 'blueiris' with pid 8292
2021-02-17 13:36:37,519 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:38,522 INFO spawned: 'blueiris' with pid 8298
2021-02-17 13:36:39,231 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:41,235 INFO spawned: 'blueiris' with pid 8304
2021-02-17 13:36:42,908 INFO success: blueiris entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-02-17 13:36:42,908 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:43,909 INFO spawned: 'blueiris' with pid 8310
2021-02-17 13:36:44,550 INFO exited: blueiris (exit status 53; not expected)
2021-02-17 13:36:45,552 INFO spawned: 'blueiris' with pid 8316
2021-02-17 13:36:45,759 WARN received SIGTERM indicating exit request
2021-02-17 13:36:45,759 INFO waiting for X11, blueiris, fluxbox, novnc, x11vnc to die
2021-02-17 13:36:45,761 INFO stopped: x11vnc (exit status 2)
2021-02-17 13:36:46,056 INFO stopped: novnc (exit status 143)
2021-02-17 13:36:46,060 INFO stopped: fluxbox (exit status 0)
2021-02-17 13:36:48,068 INFO stopped: blueiris (terminated by SIGTERM)
2021-02-17 13:36:48,091 INFO stopped: X11 (exit status 0)

I'm using the leonowski/docker-blueiris:run_as_service fork/tag, however @leonowski hasn't enabled issue tracking on his fork. The same problem applies to the dev branch here though

Discovered this while trying to troubleshoot connectivity to a camera over a macvlan docker network whose parent is a vlan subinterface.

I exec in to the container with /bin/bash.

ping my camera

"ping: command not found"

OK; apt install inetutils-ping

"Could not open lock file .... Permission denied"

Oh, right; sudo apt install inetutils-ping

"sudo: command not found"

...what?

Then try just su, but root password is not blank and at that point I'm out of ideas.

How can I poke around inside the container? I can't figure out how to elevate privileges, which just seems like such a stupid problem to have :S

This:
https://hub.docker.com/r/jshridha/blueiris/dockerfile
does not match this:
https://github.com/jshridha/docker-blueiris/blob/master/Dockerfile

I'm trying to troubleshoot some problems and this threw me for a loop.

Per instructions at https://hub.docker.com/r/jshridha/blueiris, I can run version 4 using variable BLUEIRIS_VERISION=4. I have this set, but still it is downloading version 5.

Was able to do an initial install just fine, although I was getting the same web error that was mentioned in Issue #2, - https://i.imgur.com/Pju78Y8.png - so then I restarted the container, and now it just continually just tries to run repair/modify/remove instead of actually launching blueiris. Tried running through both repair, and modify, but it just loops back around into the same wizard.

Hi,

Docker 20.5
OS: Debian 10.8

I tried both dev and master version. It runs ok for a couple min after setup and then crashes, when restarted it crashes directly (could this have something to do with storage issues maybe?)
Anyone who can tell me what I can do to fix it?

running fine, system will shutdown at some point.. when I come back up, how do I resume the container? if I docker start BlueIris, I cannot vnc connect

Recently installed this docker container and it Blue Iris keeps crashing. I would say it runs about 2 hours and then I have to re-start the container. The error from Blue Iris indicates "an assertion failed in 32 bit code". Any ideas? Thanks in advance. Other than the fact that it keeps crashing, it runs beautifully when running.

Hi,

I have audio capable cameras and cannot for the life of me get them to work. I managed to work out that the audio plays through the VNC because I heard an alert.

I can connect to the camera through VLC and hear the microphone, but it won't play live or record from within BlueIris? Perhaps I need a codec?

P.s. I can tell that BlueIris can kinda see the audio because when I click Find/Inspect it detects the same audio setting as set on my camera ('G711 A' which comes up as '64kbps G.711 a-law'). This also automatically switches to 'u-law' at the end when I change the camera to 'G711 U' (the only other option)

I don't know if this is an appropriate place to ask this question, but I have been unable to figure it out. I am new to docker and I think the issue is probably wine related, but I don't know who/where to ask for help.

When I bring up the container I get this error message (in a popup over vnc).
"There is not enough space in folder:C:\users\root\Application Data\Perspective Software\Blue Iris 5 5.0.6.9\install\ Please free some space and press Retry or press Cancel to abort the installation."

I am passing a shared nfs dataset (freenas) to the container with TB of space (-v /mnt/Shared:/root/prefix32:rw) and the VM (rancheros) running docker is installed on a virtual disk with ~200GB free. Running df from bash attached to the container shows plenty of free space. I have seen similar issues for wine, but not a solution that has allowed me to complete the blueiris installation. Any help would be appreciated, thank you!

Hi,

I've got docker-blueiris and node-deepstackai-trigger set up, inspired by this Hook Up video. I'm at the stage where BlueIris feeds low-res stills to deepstack, which can trigger high-res recordings in BlueIris. It works perfectly... if it wasn't for the BlueIris webserver being incredibly flakey. I'm new to BlueIris and don't know it's history, but it looks like this thread may refer to the same issue I'm having.

Sometimes, after starting docker-blueiris, the web UI works fine, but then it'll stop responding. Sometimes it doesn't work at all after starting the docker container. I've tried turning the webserver off and on again, or changing the port number. Looking at netstat, I've seen BI continue to listen on the original port (even though it's no longer responding), even after I've turned off the webserver or changed its port number. And on other occasions, changing the port number will make the web UI work again (on the new port). Restarting the docker container sometimes fixes the issue, sometimes not. I've also tried running it on the host network, in case it was an issue in docker, but I still saw the issue.

I tried switching to BlueIris version 4, but the install didn't work. I tried twice with the same error.

So, my questions are... is the web UI flakey for everyone else, and does the version 4 install still work for anybody else, or has it been broken but nobody's noticed because nobody uses it?

I'm so close to having all this working :)

Thanks,

Chris

I found a way to backup the configuration for both BI and the cameras. It is not optimal and I have no clue how to do it programmatically; however these are the steps I followed to be able to do this:

• Note that in my particular case I am running the container as part of my Unraid setup. So the first thing I did was to create a share and pass it to the container as a shared path. This share is where I store my recordings but also where I store the backup files that I create.

Steps to create backup:

1. Minimize BI
2. Open a terminal (right click,+ Applications-->Shell-->Bash)
3. Enter the command: wine regedit
   This command should open the windows registry
4. Expand HKEY_LOCAL_MACHINE-->Software
5. Right click on the "Perspective Software" folder
6. On the submenu click on Export
7. Save the registry to the directory that is accessible outside the container.
   Note1: Include the ".reg" filetype in the name of the file. For example: backup.reg
   Note2: Make sure that at the bottom of the export window "Selected Branch" is selected and that the path is HKEY_LOCAL_MACHINE\Software\Perspective Software
8. Click on save

This should create a reg file that you can then reuse to restore the configuration in the container if needed or if any change is made.

Steps to restore backup:

1. Start the container with a shared path that includes the reg file created before.
2. Follow the installation steps if needed
3. Before making changes in BI, minimize it.
4. Open a terminal (right click,+ Applications-->Shell-->Bash)
5. Enter the command: wine regedit
   This command should open the windows registry
6. On the Registry editor menu click on Registry and then select "Import registry file"
7. Browse for your backup file (in my case backup.reg)
8. Click on open
9. If everything went well you should se a pop up message saying that the keys and values were successfully added to the registry
10. Click on OK and exit the Registry Editor and the Terminal window
11. Maximize BI and click on the close button at the top right corner.
12. BI should start by itself a few seconds later and include the configuration and camera setup as in the previous system.

Final note. I only tested this with the Trial Version so I am not sure if this will work for full license

How can we adjust the resolution.
Can winecfg be run on initial install?

Using the vaapi dockerfiles, after creating the container and running it, I`m getting that message. Also using -v /volume1/docker/blueiris:/home/wineuser/prefix:rw, container is not creating files inside mapped volume
edit: all my containers are created with my main user uid/gid and all are working correctly but this one refuse to create files inside mapped volume. I tried to change /home/wineuser/prefix with /root/prefix on all files inside docker before creation and now is semi populating the mapped volume.

I need to downgrade to a 2020 version as my support ran out last year. When I attempt to downgrade from BlueIris, it is unable to update blueiris.exe (understandably, it is running). Closing BlueIris initiates the updater, however something is automatically restarting blueiris.exe immediately so it is unable to update.

I've been trying to get UI3 which comes with Blue Iris 5 working. Blue Iris should be loading UI3 by default at it's webserver but I am by a 404 for the login.htm page. Under the www/ folder, indeed that file does not exist.

I noticed in the main directory (Program Files/Blue Iris 5) that there is a ui3.zip. Unzipping this to www/ (unzip ui3.zip -d www/ does get the page to load but errors to occur.

Installing UI3's latest release from it's GitHub repository also causes the same issue as unzipping.

An unexpected error has occurred in Blue Iris Login (v 20 / 5.0.6.9). If you wish to report the error, please SCREENSHOT the browser now.

ReferenceError: $ is not defined
at http://censored_hostname/login.htm?page=%2F [149:3]
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0

Checking the browser console, the error appears to be at login.htm Loading failed for the <script> with source “http://192.168.3.2:81/applet/loginScripts.js?v=20-5.0.6.9”. When performing a wget or curl to this endpoint, I can see errors. This leads me to believe there is something up with the webserver.

I have to been able to reproduce this across multiple machines running this docker image. There was one time it worked, but I didn't do anything differently.

When I try to record with a h.265 camera I get this in the log. Clip: H265 Encoder Missing even if I have direct to disk enabled.

Is there anyway to add the encoder?

If I switch the camera back to h.246 it works fine, but takes up a lot of space with my 4K camera.

I'm using Blue Iris 4. The in-application 'Check for update' button results in a 'Trouble Connecting' error.

I have the same BI version (albeit x64) running natively on Windows 10 on another machine, and
the correct behaviour should be a popup saying 'Your software is up-to-date'.

TimeZone is defaulting to UTC in BlueIris. Set timezone in Docker image to proper timezone, date command shows proper time. Set environment 'TZ=America/New_York'. Still no luck. Anyone else seeing similar behavior, or am I doing something wrong?

I am hoping someone might be able to help me here. I am a little new to docker containers and am trying to get this bad boy up and running. I was able to get the BI docker container installed and running, however, I am not able to detect any of the cameras. I am not sure how the network binding works so maybe someone can help point me in the right direction here.

I am testing another project (https://github.com/thirtythreeforty/neolink) using a docker container that allows me to use Reolink D800 cameras without an NVR. I was able to get that up and the RTSP streams online, but I am not able to see my camera from this container.

Here is a screenshot from an ffprobe via the CLI of the container (Alpine Linux) streaming the camera:

Here is a screen shot from the BI container with the same command via CLI:

FYI I am using docker desktop via Windows 10 while testing.

ANY help would be greatly appreciated!

Connect to vnc.html via web browser
Click connect
black screen followed by a windows error:
extracting main application files...
Invalid command line
OK button

Hi,

Up to now I've been running Blue Iris on Windows Server in a (Hyper-V) virtual machine. One big drawback to this is that the virtualization layer does not allow the guest OS access to the hosts integrated graphics card, so no Intel QuickSync.

I'm fairly new to containerization. Can someone clarify for me, does running Blue Iris in a container like this project allow it to make use of Intel Quick Sync and improve video decoding efficiency?

Or do containers not allow pass through/access of iGFX either?

Atleast I think it's wine. I was having the error 53 problem so I switched from GPU to DEV branch, and after I installed blue iris and the wine dependencies it needed, it's giving me this error:

25/02/2021 12:16:54 created xdamage object: 0xa00024
25/02/2021 12:16:54 copy_tiles: allocating first_line at size 33
00c4:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
00c4:err:module:import_dll Library mfc140u.dll (which is needed by L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe") not found
00c4:err:module:LdrInitializeThunk Importing dlls for L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe" failed, status c0000135
003c:err:service:process_send_command service protocol error - failed to write pipe!
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"BlueIris" failed to start: 1053
00f0:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
00f0:err:module:import_dll Library mfc140u.dll (which is needed by L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe") not found
00f0:err:module:LdrInitializeThunk Importing dlls for L"C:\\Program Files\\Blue Iris 5\\BlueIris.exe" failed, status c0000135

Is there a step or dependency I missed when installing? It looks like it cant find a DLL it needs.

Thanks, and let me know if I need to provide more logs or any more info.

I am currently using the gpu branch and trying to activate my BI license.
After entering the key and hitting 'Next' it just freezes and eventually quits.

Manually restarting results in the activation window again.
I think it might be related to not being able to add the license to the registry.
Any suggestions would be appreciated, as everything I have tried didn't work.

Id like to use push notifications. Tried it on a Windows7-VM which works. On this Docker-Image it wont. I selected it and then i go to Cam-Settings to test and it says "...sent to 0 devices" or so. It should have "...sent to 1 devices"

Also the Windows are not fully displayed (no title bar, buttons missing, no scrolling). How to fix that? Thanks

Hi all - love the work on this - thankyou!

Is there any reason that there is no comment on the second branch on the master, or why the second branch isn't the master? - I burnt a LOT of hours working through the things which didn't make sense, to then find that there was a whole separate branch which had resolved 90% of the things I came up against (as simple as resolution from env).

Trying to get this docker working for first time during install on privileged docker it complains of missing Microsoft core 6.0.0

@jshridha - Can you enable the wiki for this repo? I would like to write documentation on how to use this container in it.

CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.

Could specify config by modifying:

We could also add user=root to the conf if that's how we intend to run things.

Removed

using the run command provided

Before I begin, thank you very much for the great project. Early times, but so far its looking like in my use case its stable. I just had it up for about 4 hours and so far what I need it to do (motion -> url alert -> save clip) all works great.

One issue I am having is:

My docker log is being filled with fixme:variant:get_date_format ignoring flags 402.

Any ideas why this is / how to at least hide this?

Thanks!

EDIT : I am running the :dev tag, released Feb 2021.

Is there a configuration file to map -p 81:1025 \ for external access?

I start the docker on QNAP Dockerstation and not using the command line as suggested;

docker run -d
--name="blueiris"
--privileged
--init
--restart=always
-e TZ=America/Los_Angeles
-p 8080:8080
-p 5900:5900
-p 81:81
-v /path/to/data:/home/wineuser/prefix:rw
--log-opt max-size=5m --log-opt max-file=2
jshridha/blueiris