For the first the bandwidth is paid by Microsoft via GitHub, the second from linuxserver.io via donations.
That's why I prefer the first one
this post was submitted on 04 Feb 2024
18 points (84.6% liked)
Selfhosted
40329 readers
419 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Those are two different repositories, one hosted by GitHub, the other by linuxserver.io. both are published by linuxserver, so there shouldn't be a practical difference between them.
Thanks :)
Unsolicited, but an urge for you to consider/reconsider Jellyfin over Plex
Honestly anybody using Plex should be ready to jump to Jellyfin as Plex is going down hill and Jellyfin is getting better. Just remember to donate.
Oh yes I have jellyfin ready to go whenever I actually use it for books as of right now. Just moving over from a windows laptop to Linux and using docker.
They are in fact the same image, as you can verify by comparing their digest:
$ docker pull ghcr.io/linuxserver/plex
Using default tag: latest
latest: Pulling from linuxserver/plex
Digest: sha256:476c057d677ff239d6b0b5c8e7efb2d572a705f69f9860bbe4221d5bbfdf2144
Status: Image is up to date for ghcr.io/linuxserver/plex:latest
ghcr.io/linuxserver/plex:latest
$ docker pull lscr.io/linuxserver/plex
Using default tag: latest
latest: Pulling from linuxserver/plex
Digest: sha256:476c057d677ff239d6b0b5c8e7efb2d572a705f69f9860bbe4221d5bbfdf2144
Status: Image is up to date for lscr.io/linuxserver/plex:latest
lscr.io/linuxserver/plex:latest
$
See how both images have the digest sha256:476c057d677ff239d6b0b5c8e7efb2d572a705f69f9860bbe4221d5bbfdf2144. Since the digest uniquely identifies the exact content/image, that guarantees that those images are in fact byte-for-byte identical.
Just so you know, there is also an official image: https://github.com/plexinc/pms-docker
Hardware transcoding broke for me using the official image, to be fair it was docker on a VM which I think Plex say doesn't work. The Linuxserver images work flawlessly though, so might be worth considering depending on your use case.
I switched from the official image to linuxserver.io for the better nvidia GPU setup. Had issues getting the official image to utilise the GPU properly which was solved immediately when I switched.