posted in Selfhosted

Can you run multiple servers on one machine (e.g. Raspberry Pi)?

I’m thinking about buying a Raspberry Pi to start my self-hosted journey. I have three usecases in mind: Navidrome server, Jellyfin server and a Pi-hole network ad-blocking. Can a single machine (like a Raspberry Pi) run these operations simultaneously? Thanks in advance!

enPage

Replying to @⁨SpiceDealer@lemmy.dbzer0.com⁩

Up until the point the resources available (CPU/ram/storage) become a problem.

That said, managing those apps as installations can be troublesome, which is why people like podman/docker. Updates are more contained, system updates don’t break services, and vice-versa.

A more comprehensive option is to use Proxmox or similar to manage services as a combination of Virtual Machines, LXC’S (Linux containers), and maybe podman/docker on a VM. Note that Proxmox techincally supports importing a docker container as an LXC, but this is a one-time action. Not recommended. (EDIT: For the record, there is a Proxmox on pi effort, but its community supported not Proxmox supported as of the last time I looked.)

Navidrome and pihole are the easy ones on that list also. Jellyfin itself is easy, but you aren’t going to be transcoding video on the fly, so make sure its in a format that is friendly to all of your devices, transcoding in advance if needed.

Replying to an earlier post

Depends on the Pi in terms of how much you can do, but yes.

I have a Pi 5, and I’m running Pi Hole, Nginx porxy manager, Jellyfin, Syncthing, Paperless NGX, and a full servarr stack (including Qbittorrent and a VPN). No issues; 4.6 gb out of 7.9gb ram in use, and no appreciable bottlenecks.

I would just caution that things like Jellyfin are a moveable feast - I am 1 user streaming content on my own to 1 device without issues at 4k. But more simultaneous users and if you start depending on transcoding your mileage may vary. So yes Jellyfin and other services will run fine, but any server can be put under pressure if it’s not adequate for the actual usage.

Replying to @⁨SpiceDealer@lemmy.dbzer0.com⁩

As other commenters have said yes you can run these depending on the Pi. Do note however if you need transcoding, A Pi is not recommended by jellyfin:

jellyfin.org/docs/general/…/hardware-selection#po…

Most Single Board Computers (SBC): Most SBCs (including the Raspberry Pi, especially the Raspberry Pi 5) are too slow to provide an acceptable Jellyfin experience as they often lack proper support for hardware acceleration. If you really want to run Jellyfin on an SBC, you may wish to consider models based on the following platforms: Rockchip RK3588 / RK3588S, Intel Core, Intel 12th gen N series

Replying to @⁨Squizzy@lemmy.world⁩

Official Recommendations for low power: Intel 12th gen or above N series platforms Apple M Series Mac mini Rockchip RK3588 / RK3588S SBC (Advanced Users Only)

Note 10th gen and older integrated graphics are losing support in Linux due to Intel dropping SDK support or something. Don’t buy a nuc or small PC with Intel 10 or older but if you have one it’s fine for now.

Another option would be an old laptop with dedicated graphics (e.g. e waste/recyclers). then you can get away with older than 10gen Intel since you’d be using the external graphics. Just research how to limit battery charging in the bios since it’s always going to be plugged in.

Replying to @⁨Squizzy@lemmy.world⁩

Based on those specs it sounds like it’s going to be more than capable in a homelab environment. If you’re streaming to ~5+ devices at the same time id assume it may start to struggle if it’s transcoding all of those so if you can pick or convert your media to something that doesn’t need transcoding that would be ideal.

but that looks like a solid buy. For reference I run on an old office potato and an external GPU from 2013 that I picked up for nothing a few years ago and have no problems. eventually I’ll have to upgrade when the drivers stop being supported but until then 2-3 streams max is fine for me.

Replying to an earlier post

Easily! My Pi runs PiHole and a print server and I’ll could probably run almost my entire stack in it if I wanted. Jellyfin would be the hardest due to transcoding CPU usage, but it’s probably ok for one stream at a time.

The other issue for me would be storage. Since I have a 32TB NAS I run everything that requires large storage on it, but a USB RAID attached to a Pi would probably work just fine.

The other issue is RAM. I rarely hit 8GB, but do use more than 4GB fairly regularly.

Replying to @⁨SpiceDealer@lemmy.dbzer0.com⁩

Yes yes you csn.

The old may was we would run these direct like an app on the pi.

People then came up with containers and isolated things a bit made them easy to share and configure. - dockers

Have a look for people with blogs about all the software they are running on their pi plenty of info on how.

Pi isnt the best at jellyfin server as it isnt the best at transcoding files but for direct playing without having to convert the format its enough.

Replying to @⁨xavier666@lemmy.umucat.day⁩

I always see people saying the Pi is poor for Jellyfin, but I’m running it on a 5 4GB (alongside a fair few other Docker images) and haven’t encountered any really issues. I’m only streaming 1080p and never see any stuttering or bad transcoding.

That said, I do intend to go with a SFF PC in the future as I’ve pretty quickly hit the point where it’d be better, so OP I would skip the Pi as well.

Replying to @⁨Yes_Man@lemmy.world⁩

Let me be a bit more specific. If you are doing a couple of light services + jellyfin, maybe you can pull it off. But if you have some critical latency sensitive applications + jellyfin, it can cause issues at random times.

Also, if you are ONLY hosting Jellyfin with no *arr stack, you should be fine. I made that mistake and my Pi went down to a crawl.

Test your services together, and based on that decide on the subset of services.

Replying to @⁨SpiceDealer@lemmy.dbzer0.com⁩

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters DNS Domain Name Service/System LXC Linux Containers NAS Network-Attached Storage NUC Next Unit of Computing brand of Intel small computers PCIe Peripheral Component Interconnect Express PiHole Network-wide ad-blocker (DNS sinkhole) RAID Redundant Array of Independent Disks for mass storage RPi Raspberry Pi brand of SBC SBC Single-Board Computer SSD Solid State Drive mass storage VPN Virtual Private Network

[Thread #114 for this comm, first seen 27th Sep 2026, 15:10] [FAQ] [Full list] [Contact] [Source code]

Hachyderm.ioImran Nazar ~ عمران نزر (@Two9A@hachyderm.io)3.05K Posts, 306 Following, 284 Followers · Front-end #typescript developer and general keyboard tapper; author of Internet RFC 7168 (Hypertext Coffeepot Control Protocol for teapots); occasional plumber, more than occasional #c64 #retrocomputing enthusiast, terrible at classical #piano. Header photo is a verdant scene looking over the landscape near Buxton, England, taken from a single-track country road.

Replying to @⁨SpiceDealer@lemmy.dbzer0.com⁩

A lot of people saying ditch the Pi, but it’s fairly viable depending on what exactly you want from it, so long as you get one of the newer models with plenty of RAM. Simply streaming media is relatively manageable for a Pi. It will most likely run Navidrome okay, and Jellyfin will be okay if and only if media doesn’t need to be transcoded, and you MIGHT have issues with 4K, not sure. If you stream to something like a smart TV or Fire Stick, those can typically only handle certain video formats, so if your media isn’t that type, either the server transcodes it, which the probably Pi can’t do fast enough, or playback fails. Music typically doesn’t require transcoding, so that’s why I think Navidrome should be okay. Pi-Hole is manageable and is, after all, expressly designed to be run on a Pi. It can also be run on standard hardware, so while you can do it on a Pi, you don’t need one to use Pi-Hole.

Now, that said, two main concerns about a Pi. The first is that you’ll probably eventually want to host and do more, and you may run out of resources and wish you’d just gotten a cheap mini PC instead. The second is that you really should get an external HDD or something to store as much as you can on, preferably including the OS. An SD card just is not meant to handle the constant I/O that comes with being the main drive for a full computer. It’ll eventually fail, taking all the data on it with it. I think the best way to run off an external HDD has changed since I used a Pi, so some research recommended, but what I did before was flash the EXACT SAME image to the SD card and HDD, then delete the boot partition on the HDD, expand the data partition to fill the HDD, and delete the data partition off the SD card. If you use the exact same image for both, it at least used to be that the partitions keep the same UUID, so it boots from the SD card as normal, and when told to find the other partition by UUID, it finds it on the other drive and works just fine.

Replying to @⁨SpiceDealer@lemmy.dbzer0.com⁩

One big reason why not to buy a Rqspberry Pi for Self Hosting is the price. If you want to run more heavy services (like jellyfin can be), you need the Pis with 8GB of RAM. Though those where already expensive before the sharp rise is RAM pricing. When you include a fitting power supply and a small cooler with fan (so that you don’t run into thermal throttle fast) you are probably already at like 110€ at least. For that money you can also get a used mini PC (those that companies use for their employees), that already has more power and offers better upgradebility (RAM, storage). Also for some services you might run into the problem, there is no version build for ARM devices (though that happens very rarely nowadays).

Though with the RAM pricing problem every computing device gets more expensive. Just include such mini PCs into your comparison to make a good decision.