You could write a script that just restarts your container, make sure unprivileged users cannot edit it, and do one of two things:
I noticed fedora comes with OOTB X11 DEs for gnome shell and legacy - it’s just not the first choice in the list.
K8s has a mild solution to chicken and egg situations for nodes - the nodes support ‘static manifests’ which can be pods they know how to bring up before ever connecting to the API server. So you could have your wireguard peer be brought up this way. Downside is while those static manifests show up in k8s APIs, they aren’t fully manageable since they are defined by files on disk.
Wave soldering machine - they basically suspend the whole board above a vat of solder, it bonds anywhere it can. So if they don’t need that chip on this model, it’s getting solder anyway.
Sometimes I wonder if in 75 years people will look back on our caffeine use in this generation like we currently look back at cocaine use in products in the 19th century. Until then, I continue to slurp down coffee like that is my actual job.
Yea it’s very easy to learn enough to run, it has built-in service discovery and secrets now, and writing parameterized jobs feels so much nicer than a helm chart in k8s.
10/10, would orchestrate again
I use k8s at work a lot - I choose to use Nomad at home, you may want to add that to your shortlist.
I am nearly complete migrating my ceph cluster and nomad compute cluster to arm :shrug:
My day job is a lot of kube/openshift so nomad is refreshing. Having the template blocks are amazing and makes it so that much of what helm gave me is not required. Parameterized jobs are the best once you find a good use case for them!
A year or two ago (whenever docker changed the business license of docker for Mac) I changed to podman and aliased docker=podman. It behaves the same, you would just about never know rootful podman vs docker.
Rootless podman is super cool and a much better security ideal - but comparing more apples to apples would be podman running as root vs docker.
Buildah lacks any sort of caching
… what? assuming you are using a Containerfile… what? It’s… the same as docker on layer caching. The --cache-to and --cache-from flags are particularly sweet.
Every time we see this in our legacy code we yell out: dolla-dolla bills 'yall!
(after) …ah crap it’s actually selinux…
Nomad is a breath of fresh air after working with k8s professionally.
Don’t get me wrong, love k8s, but it’s a bit much (until you need it)
someone at work got me once by changing my .bashrc to include a file that would sleep 0.001 on every command, but every time the file was sourced it would edit itself to increase the time by 0.001 seconds.
A week later I was about to toss my computer off the roof.
Ceph is excellent as a distributed storage solution - but should really have 4 machines with 2 or more drives each to reach a good level of redundancy - which is a bit much for most people on this sub.
One nice feature is it deals with heterogeneous drives well, like if you need to buy a bunch of used ones on eBay for cheap.
Probably not a good solution for your case because of the footprint - but good to be aware of it.
Are you running them from your user session? If so, when you log out it will stop your processes, unless you have enabled ‘linger’ mode.