You will learn#
- which FFmpeg build the image carries (the release archives and installers carry none), and where its source is;
- how the product finds an FFmpeg and refuses a risky one;
- which obligations come with the LGPL build.
The idea#
Vukem Video runs FFmpeg only as a separate process. It never links FFmpeg, and the pixels of a frame are composed in Go. The FFmpeg that the container image carries is one pinned LGPL build from BtbN FFmpeg-Builds, downloaded by its exact URL and verified by SHA-256 when the image is built. It is configured without --enable-gpl and without --enable-nonfree, and the build fails if either appears in the configure line. The product ships no GPL component.
The pin of this release:
| Item | Value |
|---|---|
| FFmpeg version | n9.0.2-39-g7adfbe40dc-20261031 |
| Build release tag | autobuild-2026-10-31-12-59 |
| Build scripts commit | 5031c6f1082414e53688d39e521849905071070d |
| Corresponding FFmpeg source | FFmpeg source archive |
The licence text, the configure line and these source links are inside the image, in /usr/share/doc/vukem-video/ffmpeg/ (LICENSE.txt, configure.txt and SOURCE.txt). The packages of the Debian base are listed with their licences in /usr/share/doc/vukem-video/base-image-packages.txt.
How an FFmpeg is found#
The order is fixed:
VUKEM_VIDEO_FFMPEGandVUKEM_VIDEO_FFPROBE. WhenVUKEM_VIDEO_FFMPEGis set and unusable the server reportsE_FFMPEG_MISSING; it never falls back to another one, because you asked for that binary. Both must be absolute paths to files.- The FFmpeg next to the program (bundled).
- The
PATH.
ffprobe comes from the same directory as ffmpeg. The product is tested on FFmpeg 9.0.2; another version is accepted with a warning and a version below 7 is reported as old. A missing required encoder, filter or muxer is E_FFMPEG_MISSING.
The licence of the chosen build is classified from its configure line as lgpl, gpl or nonfree. A bundled build must be lgpl. Your own build may be GPL, which is fine for your own use but not for anything you distribute, and libx264 is used only if you set VUKEM_VIDEO_ALLOW_USER_X264=true.
Quick start#
vukem-video doctor --full
vukem-video doctor --verifydoctor --full runs every check and prints the FFmpeg version, its licence class and the H.264 encoders found. --verify recomputes the digests of FFmpeg and of the downloaded helpers. It reports "matches the release" only for the pinned FFmpeg (the one in the image, or the pinned pair you place next to the program); any other FFmpeg is "your own build, not compared".
Common mistakes#
- Setting
VUKEM_VIDEO_FFMPEGto a relative path or to a directory: refused at start-up as an invalid FFmpeg path. - Shipping your own GPL FFmpeg inside an image you publish.
- Expecting the FFmpeg to be able to reach the network. It is never given a network address, and on Linux
VUKEM_VIDEO_SANDBOX=bwrapmakes the operating system enforce it.