Hi,
Not sure that’s intentional or not, but the Plex container version 1.43.7.11114-4b588ea35 published on the stable train yesterday is a preview test build from Plex and should not have been available at least on stable.
Hi,
Not sure that’s intentional or not, but the Plex container version 1.43.7.11114-4b588ea35 published on the stable train yesterday is a preview test build from Plex and should not have been available at least on stable.
File a bug report on the apps section of the true as GitHub… Normally afaik a bot pulls the latest upstream versions automatically and I may be an actual bug
Was having random issues during streaming after the update; thanks for the headsup. I’ve rolled back, hopefully all good again until the update is ready for general.
This happened with the sonarr app a few weeks back too (beta released pushed to TrueNAS stable).
Prowlarr also.
There is a reply to the bug ticket.
“If the tag does not carry enough info to differentiate, we cant do anything.
And in this case, it does not carry enough info”
Good way to get free BETA testers from TrueNAS
Sucks that there isn’t a cost-effective way to manually tag the update from IX’s end of things though.
Looks like Plex switched to listing their tags on plexinc/pms-docker - Docker Image. Latest is still 1.43.5.11079-b3b13e506. The 1.43.7.11114-4b588ea35 tag is listed as transcoder-update. It appears TrueNAS apps are looking at the raw build artifacts in AWS.
I see the ticket has been closed, despite it being flagged and acknowledged as an inappropriate build to push to users.
Could this version be removed from the iX app catalogue to save other users from mistakenly installing it?
That explains why they don’t have any information other than the version.
Not sure if CodeArtifact could bear any beta/test metadata from Plex, but this will likely happen again since Plex started to publish their preview builds on Dockerhub.
I think i’ll convert my Plex app into a custom one and point at dockerhub and/or carefully control image version.
I agree, it shouldn’t have been closed, that test version should’ve been removed from the store.
Unfortunately i can’t reopen the ticket.
Just use the public tag. This always pulls latest at every start.
Thanks, but i’ll prefer latest as i want to tightly control what version is running, also every updates i do comes with volume snapshots just in case, public may fail in that regard.
I think the iX version of the app before the current one (1.3.24 as opposed to 1.3.25) is also a beta release.
I rolled back to iX release 1.3.24 and it’s showing Plex Server as version 1.43.6.11085, however the most recent official Plex release (as of Oct 26th, according to their forum post) is actually 1.43.5.11079
Of course, the Plex container downloads a fresh binary each time it launches. So, just to confuse things, it’s actually running 1.43.5.11079, but this isn’t reflected in the version of the container ![]()
As Plex seem to be suffering from a few CVEs recently it would be really nice to have trustworthy management of these releases. Those recent CVEs all seem to be addressed in the latest release.
I think you are using the Plexpass images.
Plex provides mainly two types of images: fixed ones (Latest in Dockerhub) containing the full PMS (Plex official images in TrueNAS) and auto-updated ones that contains stubs allowing the binaries download on 3 different channels: Beta, Public and Plexpass
To carefully control what version you run, Latest is the best (if you plan snapshots, rollbacks…), also i’m not really fond of auto-build containers, security-wise we of course have to care for CVEs but also supply chain attacks gaining momentum now.