this post was submitted on 12 Nov 2023
6 points (100.0% liked)

Self-Hosted Main

511 readers
1 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
[email protected]
6
Should I go with docker containers or continue just using Arch for my home server? (alien.top)
submitted 1 year ago by [email protected] to c/[email protected]
22 comments fedilink hide all child comments
 

I mean basically the title. Currently all my services are just running directly on my arch server and it has been working well enough for me and i am super comfortable working with it. A few months back I had a minor crash of the server where the system had become not functional. I was able to recover the server to the point that my services could run but i never got the graphical part of the server going again or nextcloud running.

At this point I'm just considering wiping the os to a fresh one and starting clean to get everything working correctly again. What I'm wondering is, is it worth learning docker and deploying all my services that way or should I just continue with the way i have been doing it for years now?

I will be running the various Arr apps, Emby, NextCloud, Qbit, Homepage?, and probably a few others that i can't recall off the top of my head. Some of the services are accessed of site if that matters at all. I did briefly explore docker in the past but got stuck and my friend pushed me towards straight arch. Now I'm considering giving it another shot but wanted to hear folks here input on the pros and cons of either way

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

For me the main selling point of docker is spinning up a stable version of a container and it pulls all its dependencies which are also working. Installing things directly on the OS, at least for me, is a war of "run service; lib XX not found; apt install XX; run service; can't write to /foo/bar;" etc etc

In your case, I'd have a docker compose with all my services, and would just say docker compose up and pronto.