Has citizenship in two countries, but identifies as sovereign…

If these people actually want to be sovereign, the only way I can imagine that working is living on a boat at sea, far away from land, for the rest of their lives.

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.

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.

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)

But flight data is available - this guy just labels her N number and filters the data in a creepy way. I get that it’s probably causing her danger to have stalkers waiting at the destination for her - but those stalkers always had access to this flight data.

Seems like a workaround for Taylor would be to not own a plane and charter a different one every time. (Or do something actually environmentally minded :/)

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.

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!

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.