this post was submitted on 12 Dec 2024
46 points (81.9% liked)

Selfhosted

40696 readers
365 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hello! 😀
I want to share my thoughts on docker and maybe discuss about it!
Since some months I started my homelab and as any good "homelabing guy" I absolutely loved using docker. Simple to deploy and everything. Sadly these days my mind is changing... I recently switch to lxc containers to make easier backup and the xperience is pretty great, the only downside is that not every software is available natively outside of docker 🙃
But I switch to have more control too as docker can be difficult to set up some stuff that the devs don't really planned to.
So here's my thoughts and slowly I'm going to leave docker for more old-school way of hosting services. Don't get me wrong docker is awesome in some use cases, the main are that is really portable and simple to deploy no hundreds dependencies, etc. And by this I think I really found how docker could be useful, not for every single homelabing setup, and it's not my case.

Maybe I'm doing something wrong but I let you talk about it in the comments, thx.

(page 2) 31 comments
sorted by: hot top controversial new old
[–] macgyver@federation.red 2 points 1 week ago (3 children)

Docker compose plus using external volume mounts or using the docker volume + tar backup method is superior

load more comments (3 replies)
[–] 2xsaiko@discuss.tchncs.de 2 points 1 week ago (2 children)

Yeah, when I got started I initially put everything in Docker because that's what I was recommended to do, but after a couple years I moved everything out again because of the increased complexity, especially in terms of the networking, and that you now have to deal with the way Docker does things, and I'm not getting anything out of it that would make up for that.

When I moved it out back then I was running Gentoo on my servers, by now it's NixOS because of the declarative service configuration, which shines especially in a server environment. If you want easy service setup, like people usually say they like about Docker, I think it's definitely worth a try. It can be as simple as "services.foo.enable = true".

(To be fair NixOS has complexity too, but most of it is in learning how the configuration language which builds your operating system works, and not in the actual system itself, which is mostly standard except for the store. A NixOS service module generates a normal systemd service + potentially other files in the file system.)

I ditched nix and install software only through portage. If needed, i make my own ebuilds.

This has two advantages:

  • it removes all the messy software: i am not going to install something if I can't make the ebuild becayse the development was a mess , like everything TS/node
  • i can install, rollback, reinstall, upgrad and provision (configuration) everything using portage
  • i am getting to know gentoo and portage in great details, making the use of my desktop and laptop much much easier
load more comments (1 replies)
[–] Decq@lemmy.world 2 points 1 week ago (1 children)

I've never really like the convoluted docker tooling. And I've been hit a few times with a docker image uodates just breaking everything (looking at you nginx reverse proxy manager...). Now I've converted everything to nixos services/containers. And i couldn't be happier with the ease of configuration and control. Backup is just.a matter of pushing my flake to github and I'm done.

load more comments (1 replies)
[–] PerogiBoi@lemmy.ca 1 points 1 week ago (7 children)

I don’t like docker. It’s hard to update containers, hard to modify specific settings, hard to configure network settings, just overall for me I’ve had a bad experience. It’s fantastic for quickly spinning things up but for long term usecase and customizing it to work well with all my services, I find it lacking.

I just create Debian containers or VMs for my different services using Proxmox. I have full control over all settings that I didn’t have in docker.

[–] foremanguy92_@lemmy.ml 1 points 1 week ago

the old good way is not that bad

[–] huskypenguin@sh.itjust.works 1 points 1 week ago

Use portainer + watchtower

load more comments (5 replies)
[–] SanndyTheManndy@lemmy.world 1 points 1 week ago (8 children)

I used docker for my homeserver for several years, but managing everything with a single docker compose file that I edit over SSH became too tiring, so I moved to kubernetes using k3s. Painless setup, and far easier to control and monitor remotely. The learning curve is there, but I already use kubernetes at work. It's way easier to setup routing and storage with k3s than juggling volumes was with docker, for starters.

[–] FantasticDonkey@reddthat.com 2 points 1 week ago* (last edited 1 week ago) (1 children)

Isn’t it more effort to setup kubernetes? At work I also use k8s with Helm, Traefik, Ingress but we have an infra team that handles the details and I’m kind of afraid of having to handle the networking etc. myself. Docker-compose feels easier to me somehow.

[–] SanndyTheManndy@lemmy.world 1 points 1 week ago

Setting up k8s with k3s is barely two commands. Works out of the box without any further config. Heck, even a multi-node cluster is pretty straightforward to setup. That's what we're using at work.

load more comments (7 replies)
load more comments
view more: ‹ prev next ›