Plex support on 32bit armv7: Via linuxserver/plex docker only until Plex v1.32.4.7195 - Consider plex-server-docker-rpi as alternative receiving updates longer - openmediavault (2024)

Environment

• OMV 7 running on Armbian on Odroid HC2
• Plex: You are currently running version 1.30.0.6486 on the server "odroid-plex". Version 1.40.0.7998 is now available.
  • Plex docker container still runs fine (just outdated).
• • Was set up with via: OMV → Services → Compose → Files:

---version: "2.1"services: plex: image: lscr.io/linuxserver/plex container_name: plex network_mode: host environment: # - COMPOSE_PROJECT_NAME=plex - PUID=1000 - PGID=100 - VERSION=docker volumes: - /srv/dev-disk-by-uuid-f0233da3-473e-450d-9a18-b2ae254fc439/Plex:/config - /srv/dev-disk-by-uuid-f0233da3-473e-450d-9a18-b2ae254fc439/Shared/Videos:/videos  - /tmp-plex:/tmpfs-host-plex - /tmp:/tmpfs-host restart: unless-stopped

• Whenever I attempt docker Pull via: OMV → Services → Compose → Files → plex → Docker Pull:
  • It fails with this (linebreaks inserted by me for better readability):

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=;docker compose \--file '/srv/dev-disk-by-uuid-f0233da3-473e-450d-9a18-b2ae254fc439/dockercompose/plex/plex.yml' \--env-file '/srv/dev-disk-by-uuid-f0233da3-473e-450d-9a18-b2ae254fc439/dockercompose/plex/plex.env' \--env-file '/srv/dev-disk-by-uuid-f0233da3-473e-450d-9a18-b2ae254fc439/dockercompose/global.env' \pull 2>&1': plex Pulling no matching manifest for linux/arm/v7 in the manifest list entries

• I had performed successful docker pull actions on that container in the past.
• Above failure happened a few days ago when I was still on OMV6 before upgrading.
• Had hoped that the upgrade to OMV7 will now make the docker pull possible eventually. But error persists.
• Of course I'd like to keep the whole Plex configuration and upgrade, instead of a full fresh Plex docker installation.

Help appreciated!

Zitat von porg

See Also

plex - LinuxServer.ioHow to Run Plex via LinuxServer.io's Docker ImagePlex Media Server: Installation für Linux Ubuntu 22.04 / Debian 12How to Run Plex on Docker: The Complete Guide — RapidSeedbox

plex Pulling no matching manifest for linux/arm/v7 in the manifest list entries

Your system is armhf (32 bit). As you can see here linuxserver no longer supports that architecture for the Plex container. https://docs.linuxserver.io/images/docker-plex/

Little by little 32-bit support is disappearing. Then you have two alternatives. If your hardware supports 64-bit you can do a new 64-bit installation. If your hardware does not support 64-bit you will have no choice but to look for another 32-bit Plex container (if one exists).

Zitat von porg

image: lscr.io/linuxserver/plex

Change that line to:

image: lscr.io/linuxserver/plex:1.32.4.7195-7c8f9d3b6-ls174

Zitat von chente

If your hardware does not support 64-bit you will have no choice but to look for another 32-bit Plex container (if one exists).

All it's needed is to bind the version to the last known working on arnhf:

linuxserver/docker-plex at 1.32.4.7195-7c8f9d3b6-ls174 (github.com)

The catch:

No more updates on that container.

Or you can try this v7 one: https://hub.docker.com/r/green…ex-server-docker-rpi/tags

Zitat von Soma

See Also

overseerr - LinuxServer.io

All it's needed is to bind the version to the last known working on arnhf:

Yes, you can continue using that, but you will run out of updates. I would not do it.

Soma: You propose to keep the same Dockerfile and just tweak to 1.32.something

• So my current Plex server version 1.30.0.6486 would make it to the last supported 32bit version
• But not it make it to the advertised current version 1.40.0.7998 ?

Frepke: You propose to switch to a Dockerfile which is 32bit but still supports newer Plex so far?

• How would the migration from my existing Docker look like?
• This seems tailored for the RPi, will it also work fine for my Odroid HC2?
  (My video files are mostly H264 which need no transcoding for weaker mobile devices anyhow, so I usually do not need on the fly transcoding)
• I guess some tweaking for the new Plex will become necessary too. I recall that /tmp-plex:/tmpfs-host-plex was a tweaking that Plex writes the transcoded fragments into the RAM filesystem to avoid SD card wearing. So I would need to make sure to point the new Plex installation there too.

Zitat von porg

You propose to keep the same docker template and just tweak to 1.32.something

If you want to keep using linuxserver image, yes.

After that version, armhf was dropped.

Zitat von porg

Frepke: You propose to switch to a Dockerfile which is 32bit but still supports newer Plex so far?

• How would the migration from my existing Docker look like?
• This seems tailored for the RPi, will it also work fine for my Odroid HC2?
  (My video files are mostly H264 which need no transcoding for weaker mobile devices anyhow, so I usually do not need on the fly transcoding)
• I guess some tweaking for the new Plex will become necessary too. I recall that /tmp-plex:/tmpfs-host-plex was a tweaking that Plex writes the transcoded fragments into the RAM filesystem to avoid SD card wearing. So I would need to make sure to point the new Plex installation there too.

No, I'm not suggesting to continue using a 32-bit version at all, I'm just showing you where you might find a 32-bit version to test. Of course, you decide for yourself what you want to do, but because they're just Docker containers, it's all quite easy to test.

Frepke I took your approach as an idea how to possibly get extended use with Plex on my given 32bit hardware.

Questions/challenges that arise:

• Challenge 1: During the testing period only one of those docker containers can be up and running, as Plex requires port 32400.
  • Solution 1a: I will only run one plex container at a time and only as the client only one particular web browser per each plex variant (to not have browser caching issues due to possibly different content/hash/max-age at the same URL)
• Challenge 2: If after he testing/comparison I deem https://hub.docker.com/r/greensheep/plex-server-docker-rpi my primary choice, how do I transfer the original linuxserver-plex installation to a plex-server-docker-rpi istallation? Into the linuxserver-plex instance I have put significant metadata efforts. I assigned some additional labels/genres, assigned some movies manually to their database match, set particular posters, etc.
  • Approach 2a: Take the plex-server-docker-rpi which I took for testing, find an explicit "Library import option":
    • Solution 2a1: Scenario looks somehow supported: https://support.plex.tv/articl…nstall-to-another-system/
• Challenge 3: How I copy/move files from docker container to docker container?
  • Approach 3a: My preliminary research and intuition tells me that I will point both containers to the same Share (which point to a directory on a HDD), and there use two different Plex root directories /plex-legacy/ and /plex/, and will do my copy/move operations there.

I will wait for some feedback for some days, before I even consider to go into that endeavor.

• If no-one shares experiences, I may hesitate with that adventure, and stay with my linuxserver-plex in my currently installed version 1.30.0.6486 which overall is very satisfying to me or at most upgrade to the last supported 32bit version by tweaking the image value to lscr.io/linuxserver/plex:1.32.4.7195-7c8f9d3b6-ls174 accordingly, thanks for the hint Soma !

1 - down your actual plex

2- up plex-rpi and test it

use same config path on both, so all your DDBB are share between the two plex.

if you post here your actual plex.yml and you future plexrpi.yml, its possible to post the correct plexrpi.yml that share the config.

raulfg3 that's the simplest and best approach! Thanks!

I had the wrong conception that a docker pull creates a fresh Plex base directory by force and without possibility to intervene, and that I then have to replace that afterwards manually. But that was wrong luckily! By pointing it to an existing Plex base directory, Plex upon first launch can use that, and supposedly will detect its form an earlier version, and run an upgrade routine on that database/asset-files, if necessary.

Step by step procedure (how I imagine it):

• Stop the Old-Plex-Docker container.
• Duplicate the Plex/ base directory to Plex-Legacy/.
• Then when creating the Dockerfile for New-Plex-Docker make sure it points to the existing Plex/ base directory.
• Start the New-Plex-Docker container.
  • It will pull its files from the repo, and upon first run Plex will detect that this is a Plex base directory from an earlier version, and run an upgrade routine.
• Then your New-Plex-Docker should run. Test it over time.
  • By design Plex does not touch the source video files/folders (which reside on another Share in most setups), so all its metadata and scraped media (posters, actor-thumbnails, etc) and your customizations are persisted in the Plex base directory.
• Should you be satisifed with New-Plex-Docker, then just keep it.
• Should you be dissatisified with New-Plex-Docker, then:
  • Stop New-Plex-Docker.
  • Delete Plex/ base directory.
  • Rename Plex-Legacy/ to Plex/
  • Start Old-Plex-Docker.
  • Everything should be as it was before your experiment.

Please confirm this sums up the idea correctly.