
n8n's Distroless Image Broke Your FFmpeg Dockerfile: Two Fixes
The official n8n Docker image is distroless, so apk add fails. Two working n8n distroless ffmpeg fixes: build a custom image, or move the encode off-box.
6 articles about docker.

The official n8n Docker image is distroless, so apk add fails. Two working n8n distroless ffmpeg fixes: build a custom image, or move the encode off-box.

"n8n ffmpeg not found" means FFmpeg isn't inside your n8n Docker container. Diagnose it in three commands, then pick a Dockerfile, image, or an API call.

FFmpeg's "unknown encoder libx264" error means your binary was compiled without --enable-libx264, not that FFmpeg is broken. Diagnose it in one command.

The FFmpeg fontconfig error is a warning, not a failure: the job exits 0 and ships the wrong font. Fix it in Alpine, Debian slim, and distroless images.

A working ffmpeg docker setup: an Alpine Dockerfile, a multi-stage build, real image sizes, and the pitfalls (exit 137, fonts, codecs) nobody warns you about.

Self-hosting FFmpeg looks simple until Docker bloat, codec licensing, and scaling hit production. Compare self-hosted FFmpeg vs a cloud API.