K3s (and k8s for that matter) expect you to build a hierarchy of yaml configs, mostly because spinning up docker instances will be done in groups with certains traits applying to whole organization, certain ones applying only to most groups, but not all, and certain configs being special for certain services (http nodes added when demand is higher than x threshold).

But I wonder why you want to cluster navidrome or pihole? Navidrome would require a significant load before service load balancing is required (and non-trivial to implement), and pihole can be put behind a round-robin DNS forwarder, and also be weird to implement behind load balancing.

No reason why you can’t do it, but what do you mean by “good for normal people”?

You don’t need permission from anyone to try these things out.

This isn’t a thing because there are many comics that don’t adhere to “frames”. They overlap with others, use the whole page, etc.

But beyond this, decompress your CBR/cbz files and use imagemagick to find frames and isolate them.

ELK stack

Lolol yes, elastic was a pig for me too

deleted by creator

deleted by creator

deleted by creator

deleted by creator

The most important thing is to use your common sense, think about it an extra minute before punching holes in your fw, and keep those holes documented and to a minimum.

I have a jonsbo n1, do not buy it.

1. Cooling is insufficient. Something about the case layout makes the motherboard area not get enough ventilation and the supplied fan can’t cool 5 disks, the chassis holding the disks doesn’t allow enough air through.
2. Only room for half-height expansion card.
3. Cable routing is abysmal, with sharp edges.

That YouTube strike for Jeff geerling scares me… Twice in 6 months? For just mentioning libreelec?

We are all being driven underground by the profiteers who are ruining what was at one time a great free platform. I hope we find a way to keep our freedoms alive.

Fuck the yt police, and fuck their moms.

I rsync nightly to an old synology box. It’s in an out building, so if there’s a fire, it comes with me.

I used to run proxmox, but I wasn’t using most of its functions. I now have migrated to a couple of low power Debian machines on zfs with lxc. I use incus and ansible to manage everything, including backups.

Docker seems to have gained more ground than LXC

They aren’t really competing in the same space. LXC is more comparable to jails or openvz in that they provide an os layer, Docker does not.

I recently saw docker described in a web comic where some poor dev was bemoaning that his software “worked on his machine”, and his teacher says “then we’ll ship your machine”, meaning Docker sets up a software environment for a project to work, nothing more.

Docker was at first based on lxc, but has since moved to its own libcontainer.

You have a few questions here, which ones do you want answered?

To configure the camera, you should have defined it in the config. That you don’t know this means you should go back to the docs and read the setup section start to end.

I write my frigate clips to an NFS share. I mount it on the host and bind Mount the path in my container. You can also mount NFS directly in a container, but it comes with extra steps.

LXC is not a proxmox-specific thing. You can run lxc containers on almost any Linux and you can manage multiple containers with other software (lxd, incus, etc). At one time, docker was based on lxc, but both docker and lxc have evolved significantly since then.

LXC and docker are indeed similar, but one aims to provide an OS-level environment and the other simply a software environment.

Yes, but with an explanation.

You don’t necessarily need coding skills to “audit”, you can get q sense of the general state of things by simply reading the docs.

The docs are a good starting point to understand if there will be any issues from weird licensing, whether the author cares enough to keep the project going, etc. Also serious, repeated or chronic issues should be noted in the docs if its something the author cares about.

And remember, even if you do have a background in the coding language, the project might not be built in a style you like or agree with.

I’m pretty proficient at bash scripting, and I found the proxmox helper scripts a spaghetti mess of interdependent scripts that were simply a nightmare to follow for any particular install.

I think the overall message is do your best within your abilities.

Pwas aren’t terrible. Chrome made pwas terrible.

Wow, you just gave me flashbacks to my first Linux/unix job in 2008. Tripwire and logwatch reports to review every morning.

There’s a bunch of posts about the iptables-save function of the built-in iptables module not working in many cases, so I figured it was a safer bet to suggest the playbook include an actual command invocation.

In my personal experience, the module doesnt actually save the persistent rule in about half the cases. I haven’t looked into it much, but it seems happen more on systems where systemd iptables-firewall is present. (Not trying to start a flame war)

Generally, you set up a rule + command playbook, where the command invokes the iptables-save command.