setup-qemu-action VS clusterplex

To be clear, that article does NOT provide a solution for avoiding QEMU. I suggested it because it describes "the hard way" to get a single image multi-arch image. The github action crazy-max/ghaction-docker-buildx has been archived and replaced by docker/setup-qemu-action and docker/setup-buildx-action, which it seems like you were already using.

Second step is docker/setup-qemu-action which installs QEMU static binaries, which are used to run builders for architectures other than the host.

docker/setup-buildx-action and docker/setup-qemu-action to add support for building multi-architecture images.

# Get the repository's code - name: Checkout uses: actions/checkout@v2 # https://github.com/docker/setup-qemu-action - name: Set up QEMU uses: docker/setup-qemu-action@v1 # https://github.com/docker/setup-buildx-action - name: Set up Docker Buildx id: buildx uses: docker/setup-buildx-action@v1

docker/setup-qemu-action (This is needed for building images for other platforms)

docker/setup-qemu-action Configure QEMU to be able to compile for ARM and install the QEMU static binaries

Clusterplex

I'm also very interested in distributing transcoding jobs via https://github.com/pabloromeo/clusterplex. Have you tried that yet?

Here is a link to one of the Cluster projects: https://github.com/pabloromeo/clusterplex

I use a forked version of this: https://github.com/pabloromeo/clusterplex which has been working awesome.

This is not true. You could setup Plex in a cluster and based on which content is requested let it handle by a certain transcoding worker. You have Clusterplex or you have UnicornTranscoder. Both are actively maintained repositories. This does however require some knowledge of Linux/Kubernetes so if OP (/u/slacktopuss) doesn't know how Ubuntu and Kubernetes works, it's going to take a long time before you're up and running.

And if UnicornTranscoder isn't it, you can always look intoClusterPlex's implementation. Basically the same as how UnicornTranscoder works (Node.JS as balancer and some remote FFMPEG installs).

To see full working examples of this we can take a look at the builds of two pet projects of mine: Docker-Dogecoin and ClusterPlex.