Docker support for plexmediaserver_crack

Patches Plex Media Server running in Docker — both the official plexinc/pms-docker image and the community lscr.io/linuxserver/plex image — using the same LD_PRELOAD-on-the-PMS-exec mechanism as the native systemd install. See the top-level README and the full guide docs/DOCKER.md for the why and the troubleshooting.

Build

From the project root:

# Official image (plexinc/pms-docker)
docker build -f docker/Dockerfile.plexinc -t plex-crack:plexinc .

# Community image (lscr.io/linuxserver/plex)
docker build -f docker/Dockerfile.linuxserver -t plex-crack:lsio .

The first build downloads zig 0.13.0 and the chosen Plex base image. Subsequent builds reuse cached layers until src/, third_party/, or build.sh change. Pin the base with --build-arg PLEX_BASE_IMAGE=... if you need reproducibility across PMS updates.

Run

# plexinc (no PUID/PGID; the image runs PMS as the upstream 'plex' user)
docker run -d --name plex --network=host \
    -v /srv/plex/config:/config \
    -v /srv/plex/data:/data \
    plex-crack:plexinc

# linuxserver (honor PUID/PGID so /config and /data chown correctly on first start)
docker run -d --name plex --network=host \
    -e PUID=$(id -u) -e PGID=$(id -g) \
    -e TZ=America/Los_Angeles \
    -v /srv/plex/config:/config \
    -v /srv/plex/data:/data \
    plex-crack:lsio

Then:

curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:32400/identity   # -> 200

Patch in place (no rebuild)

If you already have a Plex container running and don't want to rebuild the image or recreate the container, plex-docker-patch.sh applies the same patch to a live container — no docker build needed, original image untouched, original container + its volumes preserved. Revertible via uninstall (a .orig copy of the s6 run file is kept).

# Default container name: "plex"
./docker/plex-docker-patch.sh install

# Custom container name
./docker/plex-docker-patch.sh install my-plex

# Revert (restores the s6 run file from its .orig)
./docker/plex-docker-patch.sh uninstall my-plex

# Status
./docker/plex-docker-patch.sh status my-plex

The script auto-detects the base image (plexinc vs LSIO) by reading the s6 run file content inside the container, so the same .so and wrapper.sh are used in both cases. Zig must be available on the host (the script invokes build.sh); a pre-existing build/plexmediaserver_crack.so is reused.

When to use which

• Dockerfile build (the docker build flow above) — best for repeat deploys, multi-host, CI/CD, immutable images. You commit a patched image and ship it.
• plex-docker-patch.sh — best for one-off patching of a running container you don't want to touch. Modifies the live container's filesystem; fully revertible via uninstall.

What's where

For docker-compose, signature drift, verification with scripts/readbitset.py, uninstall, and troubleshooting, see ../docs/DOCKER.md.

Quick troubleshooting (in-place patcher)

For deeper diagnostics (PMS exit 127, glibc vs musl ABI, LSIO /config ownership, signature drift on PMS updates), see ../docs/DOCKER.md.