docker-blueiris

Components:

• Xvfb - X11 in a virtual framebuffer
• x11vnc - A VNC server that scrapes the above X11 server
• noNVC - A HTML5 canvas vnc viewer
• Fluxbox - a small window manager
• WINE - to run Windows executables on linux
• blueiris.exe - official Windows BlueIris

version: "3.6"
services:
blueiris:
container_name: blueiris
image: packetworks/blueiris
restart: unless-stopped
privileged: true # Necessary for running the BlueIris install the first time evidently.
# init: true
devices:
-/dev/dri:/dev/dri
environment:
-LIBVA_DRIVER_NAME=iHD
ports:
-8080:8080-5900:5900 # VNC Port
-81:1025 # WebUI Port
volumes:
- blueiris:/root/prefix32:rw
-/etc/timezone:/etc/timezone:ro
-/usr/share/zoneinfo/America/New_York:/etc/localtime:ro
environment:
-PUID=1000-PGID=1000-UMASK=0077-TZ=America/New_York
logging:
options:
max-size: "10M"
max-file: "10"

• NOTES:

• The container must be run in privileged mode for the first run to allow installation of the Visual C++ components. The privileged flag can be removed after the first run.

• TZ must be specified in order to get correct time in the Windows environment.

• --init option is required as a separate script now runs inside to check if BlueIris.exe is running and kills PID 1 to stop the container.

• The /path/to/data can be a docker named volume or a local path. Set permissions for local path to 777 with chmod 777 /path/to/data. It's probably best to use a local path on your host so you can drop things in it if you need to. /home/wineuser/prefix in the container is the wine prefix environment. This is the persistent data. It can be used in normal mode and in service mode.

• The container runs as user wineuser with uid 1000.

• As Wine/BlueIris is running as a non-root user in the container, the Blue Iris Web Server cannot be exposed externally on port 81. Use a non privileged port (above 1024), for example 1025, to expose the web server externally. To do this, change the port in the settings dialog in Blue Iris after initial install.

• Service mode allows you to run blueiris as a headless, GUI-less service. VAAPI will not work. To run in service mode, you first have to run in normal mode, complete the initial install, and configure your blue iris server the way you need it to be. After you're done and no longer need to make changes, destroy the conatiner and re-launch it with the command -c /etc/supervisor/conf.d/supervisord-service.conf

• Blue Iris alerts allow you to run various things including shell commands. Wine allows you to run scripts in the Linux environment and this container has been set up to allow you to do that. See https://wiki.winehq.org/FAQ#How_do_I_launch_native_applications_from_a_Windows_application.3F

• Example docker run also has log output size limited. This will help the container storage layer from getting out of control.

Advanced Options

BlueIris version 5 is supported by default. If you'd like to run BlueIris 4, set the environmental variable: BLUEIRIS_VERISION=4

The default resolution is 1024x768x24 and is highly recommended. If you need to change the resolution set the environmental variable: RESOLUTION=1920x1080x24 or RESOLUTION=1440x768x24 etc

Known Issues:

• Saving and restoring settings backup via the BlueIris interface does not work!