From ce2b49ef73c764f95b40f8cd63e67c6bb988be52 Mon Sep 17 00:00:00 2001 From: thethreemagi Date: Sun, 2 Aug 2026 03:47:42 +0100 Subject: [PATCH] plex: pin image to 1.43.3.10828-ls316 (the exact running version) Same PMS build the database was born on. SQLite schema upgrades are one-way; a surprise :latest bump no longer gets a vote. Bump the pin deliberately when choosing to upgrade. --- plex/docker-compose.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/plex/docker-compose.yml b/plex/docker-compose.yml index 185925f..d64efc8 100644 --- a/plex/docker-compose.yml +++ b/plex/docker-compose.yml @@ -1,10 +1,10 @@ services: plex: - # Pin the tag. The migrated database is from PMS 1.43.3.10828 and SQLite - # schema upgrades are ONE-WAY — the server here must be equal or newer, and - # you do not want a surprise release performing an unexpected schema - # migration on build night. Set this to a concrete tag before first start. - image: lscr.io/linuxserver/plex:latest + # PINNED 2026-08-02 to the exact version running (and matching the migrated + # database — Windows also ran 1.43.3.10828, so no schema upgrade occurred). + # SQLite schema upgrades are ONE-WAY; upgrade by bumping this pin + # deliberately, never by riding :latest. + image: lscr.io/linuxserver/plex:1.43.3.10828-00f62d37d-ls316 container_name: plex restart: unless-stopped