sudneo

sudneo , 3 months ago to linuxmemes in Are gun designs open source?

I went to look for the video and somehow was worse than I had imagined.

sudneo , 3 months ago to Privacy in We're building a search engine to compete with DuckDuckGo. No JS, no WASM, no spying. Just a statically generated results page.

I personally like a lot the gazillion bangs also available, the personal up/downranking/blocking of websites and their quick answer is often fairly good (I mostly use it for documentation lookup). The lenses are definitely the best feature though, especially coupled with bangs.
I converted even my wife who really loves it.

sudneo , 3 months ago to Selfhosted in Simple authentication for homelab?

Thanks (grazie?)! I was looking for something similar and kanidm looks great feature wise and simple to deploy!

sudneo , 3 months ago to Selfhosted in My take on selfhosted photo management

I struggled with this for a long time, and then I just decided to use synology photos.

It has albums, tagging, geolocation, sharing. It has phone picture backup, it is inherently a backup as it's on my NAS and I back that data up again.

I want to keep the thing that I really care about the most friction free and also not too dependent on myself so that I can still experiment.

I didn't try PiGallery2 though, maybe I will have a look!

sudneo , 3 months ago to Fediverse in Hatsu: Self-hosted & Fully-automated ActivityPub Bridge for Static Sites.

Super cool project, thanks for sharing! I think I will try to integrate it with my static sites.

sudneo , 3 months ago to Selfhosted in Docker or podman?

Did it sound cold? Because I didn't mean that, I just meant to actually answer the question from my PoV. Just for the record, I also did not down vote you.

So yeah, use whatever footgun you prefer, I don't judge :)

sudneo , 3 months ago to Selfhosted in Backblaze B2 vs other storage providers to store legally ripped media

Or rustic! It is compatible with restic but has some nice additions, for example the fact that supports a config files. It makes operations a bit easier IMHO (I am currently using both).

sudneo , 3 months ago to Selfhosted in Docker or podman?

I really thought swarm was dead :)

To be honest, some kubernetes distributions make the cluster operations minimal (I use k0s managed via ansible)!

Either way, the moment you go from N containers on one box to N containers on M boxes you need to start considering how to handle stateful applications, load balancing, etc. And that in general requires knowledge on a domain which is different from having simply applications wrapped in containers locally.

sudneo , 3 months ago (edited 3 months ago) to Selfhosted in How to prioritize a container with regards to internet speed

Yeah ultimately every container has it's own veth interface, so you can do shaping using tc on those.

Edit:
I had a look at docker-tc. It does what you want, BUT. Unless your use case is complex, I would really think twice about running a tool written in bash which has access to the docker socket (I.e. trivial node escape) and runs with NET_ADMIN capability.

That's a lot of power to do something you can also do with a few lines of code executed after you start the container. Again, provided that your use case is not complex.

sudneo , 3 months ago to Selfhosted in How to prioritize a container with regards to internet speed

Cgroups have the ability to limit TCP and total network bandwidth. I don't know from the top of my mind whether this can be configured at runtime (I.e. via docker run), but you can specifcy at runtime the cgroup parent to use. This means you can pre-create the cgroup, set the limits and start the container with that parent cgroup.

You can also run some hook script after launch that adds the PID to a cgroup every time the container is launched, or possibly use tc.

I am not aware of the ability to only limit uplink bandwidth, but I have not researched this.

sudneo , 3 months ago to Selfhosted in Docker or podman?

I think k8s is a different beast, that requires way more domain specific knowledge besides server/Linux basic administration.
I do run it, but it's an evolution of a need, specifically when you want to manage a fleet of machines running containers.

sudneo , 3 months ago to Selfhosted in Docker or podman?

Because the lxc way is inherently different from the docker/podman way. It's aimed at running full systems, rather than mono process containers. It has it's use cases, but they are not as common IMHO.

sudneo , 3 months ago to Selfhosted in Docker or podman?

You have a bunch of options:

kubectl run $NAME --image=$IMAGE

this just creates a pod running the specific image. If you kill the pod, or it terminates, it won't be run again.
In general though, you probably want to do some customization before running (maybe you need volumes, secrets, env, ports, labels, securityContext, etc.) and for that you can simply let kubectl generate the boilerplate YAML and then simply make some edit:

kubectl run $NAME --image=$IMAGE --dry-run=client -o yaml > mypod.yaml
# edit mypod.yaml
kubectl create -f mypod.yaml

You can do the same with a deployment or statefulset:

kubectl create deployment $NAME -n $NAMESPACE [...] --dry-run=client -o yaml > deployment.yaml

In case you don't need anything fancy, the kubectl create subcommand allows you to create simple workload, so probably that's the answer to your question.

sudneo , 3 months ago to Selfhosted in Docker or podman?

Docker can run rootless too, see https://docs.docker.com/engine/security/rootless/

sudneo , 3 months ago to Selfhosted in Docker or podman?

I would say Docker. There is no substantial benefit in running podman, while docker is a widely adopted tool (which means more tooling in the ecosystem, easier to find answers to questions etc.). The difference is not huge tbh, and some time ago the biggest advantage for podman was being able to run rootless, while docker was stuck with a root daemon. This is not the case anymore (docker can run rootless), so I would say unless you have some specific argument to use podman, stick with docker.