News for hackers. Stuff that matters.

A comment on Google admits Kubernetes container tech is too complex. Parent comment

Re:Google admits Kubernetes container tech is too complex by fy20 on Friday February 26, 2021 @02:15AM (#26272119)
I use Swarm at home (only on a single node, because it turns out 3 are overkill for my needs) and it's been running great for 6 months so far. Before that I tried various incarnations of k8s and eventually they'd just destroy themselves up and require a rebuild (the main issue was persistent storage).

My only complaint with Swarm is there isn't an easy way to expose containers directly on the network (like host networking). I have a few containers (wireguard and minidlna) which need this, so those are running through docker-compose. I've tried macvlan but wasn't able to get that working in Swarm mode.

[ Parent | on HN ]
Re:Google admits Kubernetes container tech is too complex by lub on Friday February 26, 2021 @02:33AM (#26272213)
Did you try this?

  networks:
    - host
https://docs.docker.com/network/host/
[ Parent | on HN ]
Re:Google admits Kubernetes container tech is too complex by fy20 on Saturday February 27, 2021 @05:54AM (#26283996)
Maybe it has changed since I built it, but I wasn't able to get this working with Swarm services. I had to convert them to docker-compose to make it work. The docs suggest it should work with Swarm mode though, so maybe I need to try again.

Ideally I'd like to give each service its own IP on the network, which was possible with how I had k8s setup.

[ Parent | on HN ]
Re:Google admits Kubernetes container tech is too complex by diarrhea on Friday February 26, 2021 @05:30AM (#26273343)
Mind sharing a bit more on your home setup?

Asking because I never saw the point in multiple container replicas for simple self-hosted stuff. One container each has served me well so far [0] (Nextcloud, Bitwarden, GitLab), and if they crash, they just get restarted. Multiple containers increase throughput, supporting more users, is that it? It just sounds nightmarish in regards to storage and parallel, conflicting writes.

[0]: One container per component (web, db, cache, ...).

[ Parent | on HN ]
Re:Google admits Kubernetes container tech is too complex by fy20 on Saturday February 27, 2021 @05:49AM (#26283978)
I do have just one container of each thing, but I was originally planning to have multiple nodes. I have 3x ThinkCenter Tiny M73 (with the Pentium CPU) and thought one would be a bit underpowered for everything I wanted to run (it was for k8s), so was planning to distribute services automatically across the swarm. One node is more than enough though, so I'd actually be fine with just docker-compose, but splitting everything up into separate 'services' is nice.
[ Parent | on HN ]