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.
iluminae
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?
I was excited for this car that was all about simplicity and recyclability, sacrificing speed and features: https://www.citroen.co.uk/about-citroen/concept-cars/citroen-oli.html
But of course, they will never actually make and sell it :(
You could write a script that just restarts your container, make sure unprivileged users cannot edit it, and do one of two things:
- make a sudoers entry for your unprivileged account to call just that script as a user in the docker group with sudo
- 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.
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.
I am nearly complete migrating my ceph cluster and nomad compute cluster to arm :shrug:
This - no one can agree how long a day, week, month, year etc are!
Like sure it's 24 hours in a day but is a year 365 days? No, not technically speaking.
Time has always been really hard for programmers.
In a professional setting, sometimes the cost of developing something more performant in C is not worth it. The velocity unlocked by creating systems in Go is just incredible, after your company has built everything in C[++] for decades. I find myself creating gRPC APIs in Go to solve most design challenges, because it's stupid fast to develop and is fairly maintainable after.