Tootfinder

Opt-in global Mastodon full text search. Join the index!

@inthehands@hachyderm.io
2026-02-17 20:29:05

So I finally (what, a decade behind popular trends??) am having reason to experiment with actual use of Docker in production, and…I’m surprised at how disappointing it is.
The configuration is clumsy, a dangerous mix of boilerplate and footgun customization points. The dockerfile / compose division of labor is nonsensical; it apparently grew by accretion instead of design. There are lots of loose ends left for hosting services to tie up, and the product thus fails in what would seem to be a primary goal of avoiding hosting vendor lock-in.
Am I simply Not Getting It Yet™, or is the state of the art actually like this?

@jamesthebard@social.linux.pizza
2026-03-09 20:21:37

So, got the server in place but discovered that the Docker image that I created that has the Sisyphus client and all of the binaries like `ffmpeg`, `av1an` was not very happy. Ffmpeg crashed because it couldn't find the `libSvtAvcEnc.so.4` library which was because I had a custom version of it installed (`svt-av1-psyex`).
Got the Dockerfile fixed by installing `svt-av1-psyex` and then compiling `ffmpeg` against those libraries, then installing both `svt-av1-psyex` and `ffmpeg` int…

The worker JSON information returned from the server showing that `encoder02` is currently processing a test video using the `av1an` module.
@lil5@social.linux.pizza
2026-01-22 18:06:24

codeberg.org/lil5/brutaldon_do
Brutaldon client in a dockerfile

@jamesthebard@social.linux.pizza
2026-01-28 06:15:14

Final optimizations for the Dockerfile, and the new image is now under 500MB which is a heluva-lot better than the original 1.3GB. The results are good, images are now in Forgejo, and even better: they work.
#homelab #encoding

A screenshot of the Docker container for the Sisyphus client coming in at 493MB.