Selfhosted

56957 readers

490 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.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Ollama Server Component Recommendations (piefed.blahaj.zone)

submitted 2 days ago by irotsoma@piefed.blahaj.zone to c/selfhosted@lemmy.world

21 comments fedilink hide all child comments

I'm looking to build a low-end ollama LLM server to improve home assistant voice control, Immich image recognition and a few other services. With the current cost of hardware components like memory, I'm looking to build something small, but somewhat expandable.

I have an old micro-atx form factor computer that I'm thinking will be a good option to upgrade. I'd love recommendations on motherboards, processors, and video card combos that would likely be compatible and sufficient to run a decent server while keeping costs lower, basically, the best bang for the buck. I have a couple of M.2 SSDs I can re-purpose. Would prefer the motherboard has 2.5Gbit Ethernet, but otherwise I'm open.

Also recommendations on sites to purchase good quality memory at reasonable prices that ship to the US. I'd be willing to look at lightly used components, too.

Any advice on any of these topics would be greatly appreciated. The advice I've found has all been out of date especially with crypto fading so video cards are not as expensive, but LLM data centers eating up and reserving memory before it's even manufactured.

you are viewing a single comment's thread
view the rest of the comments

[–] chrash0@lemmy.world -1 points 2 days ago (1 children)

in a container

well there’s your issue. i get not liking the OS, but actively crippling your project will cripple your project.

containers on macOS do kinda suck

[–] Scipitie@lemmy.dbzer0.com 2 points 1 day ago (1 children)

That's sich a Mac answer it's unbelievable.

Describing "A project aimed to be agnostic of it's environment" as a design mistake and not a inherent flaw of the OS is... Just wow.

Remember in this thread it's about the pro and con of Macos as interference hardware. This is a major flaw which comes baked into the hardware. I tested it and find it an unacceptable limitation. It's important for others to know.

To state "containerization is the issue" though... Just wow.

[–] JadedBlueEyes@programming.dev 2 points 1 day ago (1 children)

Unfortunately containerisation on macos usually means running virtualized Linux, which of course is going to add overhead and cut off access to apple APIs and some hardware. So yep. There's plenty that runs natively.

[–] chrash0@lemmy.world 2 points 1 day ago

thanks for clarifying. it was hard for me to dignify such a comment with a response.

you’re also going to run into hardware acceleration issues trying to run Metal acceleration with a Linux kernel. i don’t really see a need to containerize these workloads these days anyway with tools like uv.

it’s a big pain in my ass at times trying to do web dev work with an aarch64-darwin dev env vs the target x86_64-linux. adding in hardware acceleration issues just sounds painful.

i also just personally don’t like containers. feels like bludgeon of a solution.