this post was submitted on 03 Jul 2023
14 points (93.8% liked)

Selfhosted

59391 readers
1810 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Do you host all services just from your root account with docker or do you seperate the services between user accounts with rootless docker?

Do you use podman or docker?

It's easier to just host everything from root with normal docker, but seperating services into special user account is probably way saver, at least as far as i know. Do you think ist worth going the extra step or do you just trust docker and your containers to not get exploited?

Last but not least do you use an automatic update service for your host system and your containers?

top 12 comments
sorted by: hot top controversial new old
[–] Arcidias@lemmy.world 5 points 2 years ago* (last edited 2 years ago)

I keep all my services in one docker-compose yml, and run it from a normal user account added to the docker group.

I am really conscious of what I expose to the internet though, since I already almost had a security incident.

I used to run non-standard ssh port to my machine with password authentication enabled.

Turns out I didn't know the sonarr/radarr containers came with default users, and a bruteforce attack managed to login to one of them (or something like that anyway,it's been awhile). Fortunately they have a default home of /sbin/nologin so crisis averted there, but it definitely was a big lesson for me.

Years later, the current setup is only plex, tautulli, and ombi open to the internet, and to reach everything else I use tailscale. And of course,only key-based authentication.

Oh and for updates, I run apt upgrade once in a while on the box (Ubuntu server 18.04 LTS) and for the containers, I use watchtower.

[–] kuroshi@lemmy.ramble.moe 3 points 2 years ago

Kubernetes, but I’m getting a bit tired of dealing with it. I might try using microVMs for what I’m currently using Pods, and hopefully make the whole system easier to maintain. The overhead for kubernetes is a heck of a lot more than I anticipated, I had to set up a whole second machine for what I used to be able to do on a single one.

[–] Ducks@ducks.dev 2 points 2 years ago

k3s with rancher. I was using k8s before but redid everything. K3s is overkill for what I do an causes millions of headaches but I enjoy learning through brute force.

I use k8s at work so it's good experience to run my own k3s

[–] poVoq@slrpnk.net 2 points 2 years ago

Podman managed through Quadlet container files and Systemd. Rootless where easily possible but often that requires a bit more work. Auto updates only when it is unlikely to break.

[–] ShittyKopper@lemmy.w.on-t.work 2 points 2 years ago* (last edited 2 years ago)

Rootful Podman & podman-compose. Waiting on the version of Podman that supports passt to hit Debian Bookworm or backports to attempt rootless. Deployed with Ansible except a few manual parts like creating the Postgres databases themselves.

No auto updates or notifications so far, as there seems to be a couple incompatibility issues left with Watchtower & Podman. Although since I switched CrowdSec to monitor journald instead of the Podman socket I don't really have a reason to keep the daemon running, and I think that's for the best.

[–] NewDataEngineer@lemmy.world 2 points 2 years ago* (last edited 2 years ago)

Rootless docker via Terraform. Can create all my containers with traefik and dashboard configs at the click of a button.

[–] easeKItMAn@lemmy.world 1 points 2 years ago* (last edited 2 years ago)

I’m using network overlays for individual containers and separation.
Secondly fail2ban installed on host to secure docker services. Ban FORWARDING chains specific to docker instead of INPUT chains. [fail2ban docker](Configure Fail2Ban for a Docker Container – seifer.guru) Use 2FA for services if available.

Rootless docker has limitations when it comes to port exposing, storage drivers, network overlays etc.

The host is auto-updating security batches but rebooted manually only.
Docker containers are updated manually too. I built all containers from file and don’t pull them because most are modified (plugins, minimizing sizes, dedicated user rights etc.)

[–] supersheep@lemmy.world 1 points 2 years ago

Currently, I’m just using my root account with Docker and update everything manually. I have dockcheck-web installed to check whether any updates are available (https://github.com/Palleri/DCW). From the outside everything is only accessible using Wireguard and connections have to go through a Caddy proxy in order to reach a container. Curious what other peoples setup is.

[–] sunbeam60@lemmy.one 1 points 2 years ago

Docker and a Synology NAS. Everything is accessed though a wireguard VPN.

[–] SheeEttin@lemmy.world 1 points 2 years ago

I run docker on almalinux on Proxmox. Nothing is exposed to the Internet. Yes, I do automatic updates for everything, but reboots are manual.

load more comments
view more: next ›