Closed glensc closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
You can still use older builds though we suggest you don't.
I guess plex itself still provides builds for arm arch, so could build docker image locally?
Sure if you wanted to, but our armhf baseimages are no longer supported/maintained so any bugs won't be fixed.
seems PMS itself doesn't provide package anymore?
Armv7 is armhf.
So I've come up with something like this:
docker build . --progress=plain -t plex:1.32.6.7557-1cf77d501
WARNING: Some jq and bash-foo to download if missing
root@ba32a4bac86c:/# apt info plexmediaserver
Package: plexmediaserver
Version: 1.32.6.7557-1cf77d501
Status: install ok installed
Priority: optional
Section: video
Maintainer: Plex Inc <noreply@plex.tv>
Installed-Size: 160 MB
Homepage: https://plex.tv
Download-Size: unknown
APT-Manual-Installed: yes
APT-Sources: /var/lib/dpkg/status
Description: Plex organizes all of your personal media so you can easily access and enjoy it.
You could just run the last latest image of our Plex container that works on armhf and just set the Version ENV to latest
and providing you have plexpass connected, updates will get installed on container restart.
@j0nnymoe speaks of this script (thanks!):
I prefer pre-built docker image, so re-creation wouldn't have to download and install. possibly faster startup, but definitely more predictable outcome.
Just be aware that at some point it's going to break because Plex will expect dependencies that don't exist in the armhf image, or are too out of date to be supported.
Is there an existing issue for this?
Current Behavior
You say you have deprecated armhf (As announced here),. but seems you really have REMOVED armhf support.
Typically deprecated means you can still use it. Perhaps correct the wording?
Expected Behavior
No response
Steps To Reproduce
Environment
CPU architecture
armv7l
Docker creation
Container logs