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.

Ok but we can see it says Furry Fandom as the page you are on, there is no way we just like, ignore that - right?

You could write a script that just restarts your container, make sure unprivileged users cannot edit it, and do one of two things:

1. make a sudoers entry for your unprivileged account to call just that script as a user in the docker group with sudo
2. use setuid on the script to have it execute from the docker group even when executed by users

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.

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.

As a IBM developer - ouch man, that hurts. I guess I’ll just go back my job doing… nothing (actually sounds like a sweet 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:

Did this for 3 years with a daily commute to a different state - ~13h of charging a day on 120v was far more than enough. Obviously I’m lucky enough to have a outdoor plug available to the car area but if you do it’s completely doable.

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!

• 33 nomad jobs, most being containers
• 12 physical nomad clients
  • 3 amd64 poweredge
  • 2 pi4
  • 6 Nano Pi r5c
  • 1 odroid M1
• Ceph: (nomad orchestrated)
  • 8 OSD
  • 50TB total raw disk

Make. An. Affordable. Car.

Why does every new ev for the US have to be mega deluxe luxury SUV? No one in the US is buying your affordable EV because you only sell them in Europe!

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.

And just 9 years after the idea was on adult swim.

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)

I’m glad they are doing this but in all likelihood most people who use terraform are not offering terraform to third parties on a hosted or embedded basis which is competitive with HashiCorp's products and can continue to make production use of it.

But like I said, I am glad it’s happening - as an insurance policy.

Most of the freak out I have seen I interpret as: “license says we can’t use it while competing with you but that has no real definition”

To me, it seems like an acceptable license, especially since development is happening on GitHub and they take PRs. Also the feature in the license where it reverts back to MPL after 4y is a nice security against the company doing anything else crazy restrictive - as you can plan on falling back to that version as a nuclear option.

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.