Docker container for HandBrake

This is a Docker container for HandBrake.

The GUI of the application is accessed through a modern web browser (no installation or configuration needed on the client side) or via any VNC client.

A fully automated mode is also available: drop files into a watch folder and let HandBrake process them without any user interaction.

HandBrake is a tool for converting video from nearly any format to a selection of modern, widely supported codecs.

Table of Content

• Docker container for HandBrake
  • Table of Content
  • Quick Start
  • Usage
    • Environment Variables
    • Data Volumes
    • Ports
    • Changing Parameters of a Running Container
  • Docker Compose File
  • Docker Image Update
    • Synology
    • unRAID
  • User/Group IDs
  • Accessing the GUI
  • Security
    • SSVNC
    • Certificates
    • VNC Password
  • Reverse Proxy
    • Routing Based on Hostname
    • Routing Based on URL Path
  • Shell Access
  • Access to Optical Drive(s)
  • Automatic Video Conversion
    • Multiple Watch Folders
    • Video Discs
    • Hooks
    • Temporary Conversion Directory
  • Intel Quick Sync Video
    • unRAID
  • Nightly Builds
  • Debug Builds
    • unRAID
  • Support or Contact

Quick Start

NOTE: The Docker command provided in this quick start is given as an example and parameters should be adjusted to your need.

Launch the HandBrake docker container with the following command:

docker run -d \
    --name=handbrake \
    -p 5800:5800 \
    -v /docker/appdata/handbrake:/config:rw \
    -v $HOME:/storage:ro \
    -v $HOME/HandBrake/watch:/watch:rw \
    -v $HOME/HandBrake/output:/output:rw \
    jlesage/handbrake

Where:

• /docker/appdata/handbrake: This is where the application stores its configuration, log and any files needing persistency.
• $HOME: This location contains files from your host that need to be accessible by the application.
• $HOME/HandBrake/watch: This is where videos to be automatically converted are located.
• $HOME/HandBrake/output: This is where automatically converted video files are written.

Browse to http://your-host-ip:5800 to access the HandBrake GUI. Files from the host appear under the /storage folder in the container.

Usage

docker run [-d] \
    --name=handbrake \
    [-e <VARIABLE_NAME>=<VALUE>]... \
    [-v <HOST_DIR>:<CONTAINER_DIR>[:PERMISSIONS]]... \
    [-p <HOST_PORT>:<CONTAINER_PORT>]... \
    jlesage/handbrake

Environment Variables

To customize some properties of the container, the following environment variables can be passed via the -e parameter (one for each variable). Value of this parameter has the format <VARIABLE_NAME>=<VALUE>.

Data Volumes

The following table describes data volumes used by the container. The mappings are set via the -v parameter. Each mapping is specified with the following format: <HOST_DIR>:<CONTAINER_DIR>[:PERMISSIONS].

Ports

Here is the list of ports used by the container. They can be mapped to the host via the -p parameter (one per port mapping). Each mapping is defined in the following format: <HOST_PORT>:<CONTAINER_PORT>. The port number inside the container cannot be changed, but you are free to use any port on the host side.

Changing Parameters of a Running Container

As can be seen, environment variables, volume and port mappings are all specified while creating the container.

The following steps describe the method used to add, remove or update parameter(s) of an existing container. The general idea is to destroy and re-create the container:

1. Stop the container (if it is running):

docker stop handbrake

2. Remove the container:

docker rm handbrake

3. Create/start the container using the docker run command, by adjusting parameters as needed.

NOTE: Since all application's data is saved under the /config container folder, destroying and re-creating a container is not a problem: nothing is lost and the application comes back with the same state (as long as the mapping of the /config folder remains the same).

Docker Compose File

Here is an example of a docker-compose.yml file that can be used with Docker Compose.

Make sure to adjust according to your needs. Note that only mandatory network ports are part of the example.

version: '3'
services:
  handbrake:
    image: jlesage/handbrake
    build: .
    ports:
      - "5800:5800"
    volumes:
      - "/docker/appdata/handbrake:/config:rw"
      - "$HOME:/storage:ro"
      - "$HOME/HandBrake/watch:/watch:rw"
      - "$HOME/HandBrake/output:/output:rw"

Docker Image Update

Because features are added, issues are fixed, or simply because a new version of the containerized application is integrated, the Docker image is regularly updated. Different methods can be used to update the Docker image.

The system used to run the container may have a built-in way to update containers. If so, this could be your primary way to update Docker images.

An other way is to have the image be automatically updated with Watchtower. Whatchtower is a container-based solution for automating Docker image updates. This is a "set and forget" type of solution: once a new image is available, Watchtower will seamlessly perform the necessary steps to update the container.

Finally, the Docker image can be manually updated with these steps:

1. Fetch the latest image:

docker pull jlesage/handbrake

2. Stop the container:

docker stop handbrake

3. Remove the container:

docker rm handbrake

4. Create and start the container using the docker run command, with the the same parameters that were used when it was deployed initially.

Synology

For owners of a Synology NAS, the following steps can be used to update a container image.

1. Open the Docker application.
2. Click on Registry in the left pane.
3. In the search bar, type the name of the container (jlesage/handbrake).
4. Select the image, click Download and then choose the latest tag.
5. Wait for the download to complete. A notification will appear once done.
6. Click on Container in the left pane.
7. Select your HandBrake container.
8. Stop it by clicking Action->Stop.
9. Clear the container by clicking Action->Clear. This removes the container while keeping its configuration.
10. Start the container again by clicking Action->Start. NOTE: The container may temporarily disappear from the list while it is re-created.

unRAID

For unRAID, a container image can be updated by following these steps:

1. Select the Docker tab.
2. Click the Check for Updates button at the bottom of the page.
3. Click the update ready link of the container to be updated.

User/Group IDs

When using data volumes (-v flags), permissions issues can occur between the host and the container. For example, the user within the container may not exist on the host. This could prevent the host from properly accessing files and folders on the shared volume.

To avoid any problem, you can specify the user the application should run as.

This is done by passing the user ID and group ID to the container via the USER_ID and GROUP_ID environment variables.

To find the right IDs to use, issue the following command on the host, with the user owning the data volume on the host:

id <username>

Which gives an output like this one:

uid=1000(myuser) gid=1000(myuser) groups=1000(myuser),4(adm),24(cdrom),27(sudo),46(plugdev),113(lpadmin)

The value of uid (user ID) and gid (group ID) are the ones that you should be given the container.

Accessing the GUI

Assuming that container's ports are mapped to the same host's ports, the graphical interface of the application can be accessed via:

• A web browser:

http://<HOST IP ADDR>:5800

• Any VNC client:

<HOST IP ADDR>:5900

Security

By default, access to the application's GUI is done over an unencrypted connection (HTTP or VNC).

Secure connection can be enabled via the SECURE_CONNECTION environment variable. See the Environment Variables section for more details on how to set an environment variable.

When enabled, application's GUI is performed over an HTTPs connection when accessed with a browser. All HTTP accesses are automatically redirected to HTTPs.

When using a VNC client, the VNC connection is performed over SSL. Note that few VNC clients support this method. SSVNC is one of them.

SSVNC

SSVNC is a VNC viewer that adds encryption security to VNC connections.

While the Linux version of SSVNC works well, the Windows version has some issues. At the time of writing, the latest version 1.0.30 is not functional, as a connection fails with the following error:

ReadExact: Socket error while reading

However, for your convenience, an unofficial and working version is provided here:

https://github.com/jlesage/docker-baseimage-gui/raw/master/tools/ssvnc_windows_only-1.0.30-r1.zip

The only difference with the official package is that the bundled version of stunnel has been upgraded to version 5.49, which fixes the connection problems.

Certificates

Here are the certificate files needed by the container. By default, when they are missing, self-signed certificates are generated and used. All files have PEM encoded, x509 certificates.

NOTE: To prevent any certificate validity warnings/errors from the browser or VNC client, make sure to supply your own valid certificates.

NOTE: Certificate files are monitored and relevant daemons are automatically restarted when changes are detected.

VNC Password

To restrict access to your application, a password can be specified. This can be done via two methods:

• By using the VNC_PASSWORD environment variable.
• By creating a .vncpass_clear file at the root of the /config volume. This file should contain the password in clear-text. During the container startup, content of the file is obfuscated and moved to .vncpass.

The level of security provided by the VNC password depends on two things:

• The type of communication channel (encrypted/unencrypted).
• How secure the access to the host is.

When using a VNC password, it is highly desirable to enable the secure connection to prevent sending the password in clear over an unencrypted channel.

ATTENTION: Password is limited to 8 characters. This limitation comes from the Remote Framebuffer Protocol RFC (see section 7.2.2). Any characters beyond the limit are ignored.

Reverse Proxy

The following sections contain NGINX configurations that need to be added in order to reverse proxy to this container.

A reverse proxy server can route HTTP requests based on the hostname or the URL path.

Routing Based on Hostname

In this scenario, each hostname is routed to a different application/container.

For example, let's say the reverse proxy server is running on the same machine as this container. The server would proxy all HTTP requests sent to handbrake.domain.tld to the container at 127.0.0.1:5800.

Here are the relevant configuration elements that would be added to the NGINX configuration:

map $http_upgrade $connection_upgrade {
	default upgrade;
	''      close;
}

upstream docker-handbrake {
	# If the reverse proxy server is not running on the same machine as the
	# Docker container, use the IP of the Docker host here.
	# Make sure to adjust the port according to how port 5800 of the
	# container has been mapped on the host.
	server 127.0.0.1:5800;
}

server {
	[...]

	server_name handbrake.domain.tld;

	location / {
	        proxy_pass http://docker-handbrake;
	}

	location /websockify {
		proxy_pass http://docker-handbrake;
		proxy_http_version 1.1;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection $connection_upgrade;
		proxy_read_timeout 86400;
	}
}

Routing Based on URL Path

In this scenario, the hostname is the same, but different URL paths are used to route to different applications/containers.

For example, let's say the reverse proxy server is running on the same machine as this container. The server would proxy all HTTP requests for server.domain.tld/handbrake to the container at 127.0.0.1:5800.

Here are the relevant configuration elements that would be added to the NGINX configuration:

map $http_upgrade $connection_upgrade {
	default upgrade;
	''      close;
}

upstream docker-handbrake {
	# If the reverse proxy server is not running on the same machine as the
	# Docker container, use the IP of the Docker host here.
	# Make sure to adjust the port according to how port 5800 of the
	# container has been mapped on the host.
	server 127.0.0.1:5800;
}

server {
	[...]

	location = /handbrake {return 301 $scheme://$http_host/handbrake/;}
	location /handbrake/ {
		proxy_pass http://docker-handbrake/;
		location /handbrake/websockify {
			proxy_pass http://docker-handbrake/websockify/;
			proxy_http_version 1.1;
			proxy_set_header Upgrade $http_upgrade;
			proxy_set_header Connection $connection_upgrade;
			proxy_read_timeout 86400;
		}
	}
}

Shell Access

To get shell access to the running container, execute the following command:

docker exec -ti CONTAINER sh

Where CONTAINER is the ID or the name of the container used during its creation (e.g. crashplan-pro).

Access to Optical Drive(s)

By default, a Docker container doesn't have access to host's devices. However, access to one or more device can be granted with the --device DEV parameter.

Optical drives usually have /dev/srX as device. For example, the first drive is /dev/sr0, the second /dev/sr1, and so on. To allow HandBrake to access the first drive, this parameter is needed:

--device /dev/sr0

To easily find devices of optical drives, start the container and look at its log for messages similar to these ones:

...
[cont-init.d] 95-check-optical-drive.sh: executing...
[cont-init.d] 95-check-optical-drive.sh: looking for usable optical drives...
[cont-init.d] 95-check-optical-drive.sh: found optical drive /dev/sr0, but it is not usable because is not exposed to the container.
[cont-init.d] 95-check-optical-drive.sh: no usable optical drive found.
[cont-init.d] 95-check-optical-drive.sh: exited 0.
...

Since HandBrake can decrypt DVD video discs, their conversion can be performed directly from the optical device. From the graphical interface, click the Open Source button and browse through the file system to find your optical drive device (e.g. /dev/sr0).

Automatic Video Conversion

This container has an automatic video converter built-in. This is useful to batch-convert videos without user interaction.

Basically, files copied to the /watch container folder are automatically converted by HandBrake to a pre-defined video format according to a pre-defined preset. Both the format and the preset are specified via environment variables:

See the Environment Variables section for details about setting environment variables.

NOTE: A preset is identified by its category and its name.

NOTE: All default presets, along with personalized/custom ones, can be seen with the HandBrake GUI.

NOTE: Converted videos are stored, by default, to the /output folder of the container.

NOTE: The status and progression of conversions performed by the automatic video converter can be seen from both the GUI and the container's log. Container's log can be obtained by executing the command docker logs handbrake, where handbrake is the name of the container. Also, full details about the conversion are stored in /config/log/hb/conversion.log (container path).

Multiple Watch Folders

If needed, up to 4 additionnal watch folders can be used:

• /watch2
• /watch3
• /watch4
• /watch5

This is useful in scenarios where videos need to be converted by different presets. For example, one could use a watch folder for movies and another watch folder for TV shows, both having different encoding quality requirements.

By default, additional watch folders inherits the same settings has the main one (/watch). A setting for a particular watch folder can be overrided by adding its index to the corresponding environment variable name.

For example, to set the HandBrake preset used to convert videos in /watch2, the environment variable AUTOMATED_CONVERSION_PRESET_2 is used. AUTOMATED_CONVERSION_PRESET_3 is used for /watch3, and so on.

All settings related to the automatic video converter can be overrided for each additional watch folder:

• AUTOMATED_CONVERSION_PRESET
• AUTOMATED_CONVERSION_FORMAT
• AUTOMATED_CONVERSION_SOURCE_STABLE_TIME
• AUTOMATED_CONVERSION_SOURCE_MIN_DURATION
• AUTOMATED_CONVERSION_OUTPUT_DIR
• AUTOMATED_CONVERSION_OUTPUT_SUBDIR
• AUTOMATED_CONVERSION_OVERWRITE_OUTPUT
• AUTOMATED_CONVERSION_KEEP_SOURCE
• AUTOMATED_CONVERSION_VIDEO_FILE_EXTENSIONS
• AUTOMATED_CONVERSION_NON_VIDEO_FILE_ACTION
• AUTOMATED_CONVERSION_NON_VIDEO_FILE_EXTENSIONS

Video Discs

The automatic video converter supports video discs, in the following format:

• ISO image file.
• DVD video disc folder containing the VIDEO_TS folder.
• Blu-ray video disc folder containing the BDMV folder.

Note that folder names are case sensitive. For example, video_ts, Video_Ts or Bdmv won't be treated as discs, but as normal directories.

When the source is a disc folder, the name of the converted video file will match to one of its folder. For example, /watch/MyMovie/VIDEO_TS will produce a video file with name MyMovie.mp4.

Video discs can have multiple titles (the main movie, previews, extras, etc). In a such case, each title is converted to its own file. These files have the suffix .title-XX, where XX is the title number. For example, if the file MyMovie.iso has 2 titles, the following files would be generated:

• MyMovie.title-1.mp4
• MyMovie.title-2.mp4

It is possible to ignore titles shorted than a specific amount of time. By default, only titles longer than 10 seconds are processed. This duration can be adjusted via the AUTOMATED_CONVERSION_SOURCE_MIN_DURATION environment variable. See the Environment Variables section for details about setting environment variables.

Hooks

Custom actions can be performed using hooks. Hooks are shell scripts executed by the automatic video converter.

NOTE: Hooks are always invoked via /bin/sh, ignoring any shebang the script may have.

Hooks are optional and by default, no one is defined. A hook is defined and executed when the script is found at a specific location.

The following table describe available hooks:

During the first start of the container, example hooks are installed in /config/hooks/. Example scripts have the suffix .example. For example, you can use /config/hooks/post_conversion.sh.example as a starting point.

NOTE: Keep in mind that this container has the minimal set of packages required to run HandBrake. This may limit actions that can be performed in hooks.

Temporary Conversion Directory

A video being converted is written in a hidden, temporary directory under the root of the output directory (/output by default). Once a conversion successfully terminates, the video file is moved to its final location.

This feature can be useful for scenarios where the output folder is monitored by another application: with proper configuration, one can make sure this application only "sees" the final, converted video file and not the transient versions.

If the monitoring application ignores hidden directories, then nothing special is required and the application should always see the final file.

However, if the monitoring application handles hidden directories, the automatic video converter should be configured with the AUTOMATED_CONVERSION_OUTPUT_SUBDIR environment variable sets to a subdirectory. The application can then be configured to monitor this subdirectory. For example, if AUTOMATED_CONVERSION_OUTPUT_SUBDIR is set to TV Shows and /output is mapped to $HOME/appvolumes/HandBrake on the host, $HOME/appvolumes/HandBrake/TV Shows should be monitored by the application.

Intel Quick Sync Video

Intel Quick Sync Video is Intel's brand for its dedicated video encoding and decoding hardware core. It is a technology that is capable of offloading video decoding and encoding task to the integrated GPU, thus saving the CPU usage to do other tasks. As a specialized hardware core on the processor die, Quick Sync offers a much more power efficient video processing which is much superior to video encoding on a CPU.

For HandBrake to be able to use hardware-accelerated encoding, the following are required:

• Have a compatible Intel processor. To determine if your CPU has the Quick Sync Video hardware, consult this list from the Intel Ark website. The model name of your processor is printed to the container's log during its startup. Look for a message like this:

  [cont-init.d] 95-check-qsv.sh: Processor: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
  

• The Intel i915 graphic driver must be loaded on the host.
• The /dev/dri device must be exposed to the container. This is done by adding the --device /dev/dri parameter to the docker run command.

When Intel Quick Sync Video is properly enabled, HandBrake offers the following video encoder:

H.264 (Intel QSV)

If this encoder is not part of the list, something is wrong and looking at the container's log can give more details about the issue.

NOTE: In most cases, HandBrake can successfully access the /dev/dri device without changing anything on the host side. This is possible because the user under which the container is running is automatically added to the group owning the /dev/dri device. However, this method doesn't work if the device is owned by the group root. The problem can be fixed using one of the following methods:

• Running the container as root (USER_ID=0).
• Adding, on the host, read/write permissions for all to the /dev/dri device:

  sudo chmod a+wr /dev/dri/*
  

• Changing, on the host, the group owning the /dev/dri device. For example, to change the group to video:

  sudo chown root:video /dev/dri/*
  

unRAID

The Intel i915 driver is already included in unRAID. To automatically load the driver during the startup of the host, the following lines must be added to /boot/config/go:

# Load the i915 driver.
modprobe i915

Nightly Builds

HandBrake nightly builds are based on the latest development code, which means they may or may not be stable.

The latest development version is available by using the dev-latest Docker image tag. For other specific development versions, look at available tags on Docker Hub.

When creating the container, the tag needs to be appended to the name of the Docker image, like this:

docker run [OPTIONS..] jlesage/handbrake:dev-latest

Debug Builds

Debug builds can be used to better investigate problems that can occur with HandBrake. These builds have HandBrake compiled in debug mode and all symbols are kept.

The main use case of debug builds is debugging a crash. To do this, a core dump needs to be generated when HandBrake crashes. To make sure this core dump is properly generated, two things are required:

1. Core dumps must be enabled. This is done by setting the maximum size of cores via the --ulimit core=-1 parameter of the docker run command. A value of -1 mean "unlimited".

2. Location of the cores must be set. This can be done by executing the following command on the host:

   echo 'CORE_PATTERN' | sudo tee /proc/sys/kernel/core_pattern
   

   Where CORE_PATTERN is the template that defines the naming of core dump files. For example, to set the files in the configuration volume of the container (for easy retrieval from the host), use the pattern /config/core.%e.%t.

   NOTE: Because a core file contains the complete memory layout of an application, it is created with restrictive permissions. If another user other than the one used to run HandBrake needs to access the core file, permissions must be changed by executing chmod a+r CORE, where CORE is the path to the core file.

   NOTE: Since the core dump files pattern is shared between the host and the container, you may want to revert to the original pattern once done.

   NOTE: The current value of the pattern can be obtained by executing cat /proc/sys/kernel/core_pattern.

Debug builds are available by using Docker image tags with the debug suffix. Make sure to look at available tags on Docker Hub.

When creating the container, the tag needs to be appended to the name of the Docker image, like this:

docker run [OPTIONS..] jlesage/handbrake:v1.14.3-debug

unRAID

On systems running unRAID, the --ulimit core=-1 parameter can be added to the Extra Parameters field of the container settings.

Support or Contact

Having troubles with the container or have questions? Please create a new issue.

For other great Dockerized applications, see https://jlesage.github.io/docker-apps.