Install Ffmpeg In Docker Container

Ubuntu team has its own vision for the snap ( service and that’s why they have moved the really big and difficult to maintain Chromium browser package in the snap package. Unfortunately, the snap has many issues with docker containers and in short, it is way difficult to run snap in a docker container. The user may just want not to mess with snap packages (despite this is the future according to the Ubuntu team) or like most developers they all need a browser for their tests executed in a container.
Whether you are a developer or an ordinary user this article is for you, who wants Chromium browser installed not from the snap service under Ubuntu 20.04 LTS!
There are multiple options, which could end up with a Chromium browser installed on the system, not from the snap service:

  1. Install Ffmpeg In Docker Container Free
  2. Install Ffmpeg In Docker Container Space
  3. Install Ffmpeg In Docker Container Linux
  4. Install Ffmpeg In Docker Container Box
  5. Install Ffmpeg In Docker Containers
  6. Install Ffmpeg In Docker Container Free
  1. Using Debian package and Debian repository. The problem here is that using simultaneously Ubuntu and Debian repository on one machine is not a good idea! Despite the hack, Debian packages are with low priority –
  2. Using Google Chrome – It is just a single Debian package, which provides Chromium-like browser and all dependencies requesting the Chromium browser package are fulfilled.
  3. Using Chromium team dev or beta PPA ( for the nearest version if still missing Ubuntu packages for Focal (Ubuntu 20.04 LTS).
  4. more options available?

This article will show how to use Ubuntu 18 (Bionic) Chromium browser package from Chromium team beta PPA under Ubuntu 20.04 LTS (Focal). Bionic package from the very same repository of Ubuntu Chromium team may be used, too.

$ docker run -v=`pwd`:/tmp/ffmpeg opencoconut/ffmpeg -i localfile.mp4 out.webm This command is too long, so let’s create an alias by adding this line at the end of your /.bashrc or /.zshrc file.

All dependencies will be downloaded from the Ubuntu 20.04 and just several Chromium-* packages will be downloaded from the Chromium team PPA Ubuntu 19 repository. The chances to break something are really small compared to the options 1 above, which uses the Debian packages and repositories. Hope, soon we are going to have focal (Ubuntu 20.04 LTS) packages in the Ubuntu Chromium team PPA!



An example of a Dockerfile installing Chromium (and python3 selenium for automating web browser interactions)

First command adds the repository key and the repository to the Ubuntu source lists. Note we are adding the “bionic main”, not “focal main”.
From the all dependencies of the Bionic chromium-browser only three packages are pulled from the Bionic repository and all other are from the Ubuntu 20 (Focal):

Here is the whole Dockerfile sample file:

Follow these steps to install video encoding to your docker container. Step-by-step instructions:. Find the name of the container you want to install libav-tools to by executing docker ps -a. Once you get the name, use following syntax if you are running the same WordPress image that I have shown above. Docker exec wptfphotos apt-get install. Sep 26, 2021 Install Ffmpeg In Docker Container Linux. Using FFmpeg with the Portable Version. The portable version doesn't come with FFmpeg by default, so to install FFmpeg you have three options. Use the package manager homebrew by typing brew install ffmpeg into your Terminal (here's how to install homebrew if you don't have it already.

Desktop install

The desktop installation is almost the same as the Dockerfile above. Just execute the following lines:

#!/bin/bash echo '. installing ffmpeg.' apk add -no-cache ffmpeg Custom Services. There might also be a need to run an additional service in a container alongside what we already package. Similarly to the custom scripts, just create a new directory at /config/custom-services.d. The files in this directory should be named after the. I'd like to add the homebridge-camera-ffmpeg plugin to the docker which loads but fails when triggered by the IOS I imagine that the container cannot work with the standard synology ffmpeg package (unlike other packages like mosquitto), and that ffmpeg needs to be installed within the docker container.

Throubleshooting – snap install of Chromium in Docker

This is the original problem – at present, the snap store does not work executed in docker, so apt cannot Chromium browser.

In fact, the installation just hangs in checking connectivity with the snap store.

And the package is never installed.

This article explains how to install Docker on a Raspberry Pi, how to build a simple image, and how to run a container based on it.

Update 19/12/20: Unfortunately this procedure is temporarily broken. Due to a bug in libccomp2 and for other reasons, the docker build command fails with signature errors, and I have not been able to find a stable, repeatable solution. Hopefully it will start working again with future Raspian/Debian updates. When that happens the article will be updated. For now, do not use the following procedure.

Docker provides a mobile execution environment in which to run software. It is a very popular container technology. Docker is useful in the rapid deployment of applications and in application isolation. It is a valuable tool for developers, users and systems administrators. In this procedure, it will be used to install a simple video processing application called “comskip“.

Although the article is entitled Install Docker on Raspberry Pi, this procedure will work unaltered on most Linux distros, which is one of the advantages of Docker.

Besides acting as a demonstration for those wanting to learn about Docker, this article is aimed at readers of my previous articles How to Watch and Record Live TV with a Raspberry Pi and How to Install Comskip on a Rasperry Pi (without Docker).

Install Docker

Install ffmpeg in docker container box

Use the following command to install Docker.

Install Ffmpeg In Docker Container Free

wait a few minutes for the install to complete.

Create a Docker File

A Docker image will be created from the definition below. First, create a sub directory:

Now, using vi, nano or another editor, create a new file. Name the file “Dockerfile” and make its contents as below:

Save the file.

Build the Image

Build the image as follows:

(Note. If the command failed with errors like “Err:1 focal InRelease. At least one invalid signature was encountered.”, it’s likely due to a known bug in libseccom2. For a fix, see the Appendix)

This command will perform many tasks. The standard base image “ubuntu” is pulled (downloaded) from Docker Hub. Several libraries and tools are installed into it. Next, the comskip source code is obtained (cloned) from Github. Lastly, comskip is compiled. The whole process took about 16 minutes on a Pi2, so be patient.

Note the last four lines of the Docker file are commented out and don’t do anything for the moment. More on that later.

Run the Docker Container

Install Ffmpeg In Docker Container Space

We have freshly built Docker image, containing all of the bits and pieces needed to run comskip. Although many items of software have been installed, eg. ffmpeg and git, these have not been installed onto your Pi. Instead, they have been installed into the Docker image. All that has been installed on the Pi is Docker itself.

In order to bring that image to life, run a container. Run a container based on the image as follows.

The container is running and you are left with a prompt. This is a container shell and commands issued here are executed in the container, not directly on the host (your Pi).

Run Comskip

Install Ffmpeg In Docker Container Linux

The command we want to run is comskip. For demonstration, I have uploaded a video file into the container.

Success! The video file, a 50 minute episode of Minder, was processed in 667 seconds, about 11 minutes.

Access to Video Files

Comskip can be used to process TV recordings created by apps like OSMC and Kodi. If you have a media center PC or similar, its recordings folder could be mounted into the Docker container. If you have shared out the recordings directory, eg. by configuring Samba on an OSMC server, then the last 4 lines of the Docker file can be used to mount the share.

To try it, uncomment the last 4 lines in the Docker file. And edit the last line, replacing <osmc IP address> with your media centre’s IP. Re-run the docker build and docker run commands. Then, at the container prompt, mount the share:


Exit the Container

When you are finished messing around in the Docker container, type exit or press ctrl-d.

You are returned to the Pi command prompt. To run the container again, just repeat the docker run command above. Incidentally, the “–cap add” flags in that command are needed only so that the mount command works within the container.


Docker has different benefits in different situations. Here, it enabled us to install a software package on our system, and its fairly complicated set of dependencies, without splattering new libraries and modules all over the system. ffmpeg, libtool and other items named in the Dockerfile (under ENV PACKAGES) were installed within the Docker image, not into the Pi’s system folders. Out host system thus remains “clean” and unchanged.

When the Docker container exits, any files we created on the fly are lost, including files created by comskip. Storage is ephemeral. One solution is to use Docker storage volumes. Another is to mount a remote data area directly into the container, which is what we did.


libseccomp2 Bug (December 2020)

If the docker build resulted in errors like “Err:1 focal InRelease. At least one invalid signature was encountered.“, it will most likely be due to a known bug in libseccom2. The bug has been fixed but the fix has not yet made its way into the stable Debian repositories. If you get this error, you can forcibly update libseccomp2 from the unstable repos. (at your own risk – they are called “unstable”, after all. I recommend proceeding only on a system that can be rebuilt and isn’t performing a critical function for you).

Check your current version of libseccomp2. I encountered the error with version 2.3.3-4:

Install Ffmpeg In Docker Container Box

Download the latest version from the Debian Sid. You will need to choose the right architecture for your device and also check your installed libc version is high enough (compare the output of “dpkg -l libc6” on your system with the libc notes on the aforementioned page). I am using a Raspberry Pi 4, so the architecture is “armf” (as it is for the Pi 2 and Pi 3). I downloaded libseccomp2 version 5.2.0-3 from the armf page, using “wget” and choosing a mirror located here in the UK. Alternatively, you could download with a browser.

Note this URL is likely to change and might no longer work when you are reading this.

Install the package:

Check the new version:

If you return to the main procedure, the docker build command should now work

Install Ffmpeg In Docker Containers

Thanks to Igor Velkov for posting this solution on AskUbuntu.

Install Ffmpeg In Docker Container Free