virtual IP addresses
Yeah, metallb.
virtual IP addresses
Yeah, metallb.
The container is reproducible. Container configuration is in version control. That leaves you with the volumes mounted into the container, which you back up like any other disk.
Rant: We’re living in a time where curl | bash
has become normalized. This generation’s security practices are fucked.
Back to the topic: I see it as a problem of not enough education and too much trust. People are not taught how to verify the authenticity and legitimacy of software, and put too much trust in claims of authority. It’s not just a consumer problem either, look at the CrowdStrike incident: people in the industry knew it was shit, but the decision makers kept trusting it because they are a big name. How did they become a big name? The same way a lot of other companies do, by bribing the early decision makers into using them.
Back to consumers: it doesn’t help that there’s no first class sandboxing features. Both Android and iOS rely heavily on app store controls. Sure, there are some system controls, but the user has barely any agency over them.
It’s not that Seagate improved (which it may have), it’s more that WD has noticeably declined. It’s not a race to the bottom (yet), but there’s effectively no competition any more, so they aren’t incentivised to improve quality.
I think there’s a mistake, I can’t fit “neovim” into 8 across.
Figure out the uid/gid (numeric) for the user in lxc, then change the data permissions to those.
Use -m
and limit the build job’s memory so it doesn’t kill the docker daemon.
Primitive Technology.
I’m out of the loop. How does Carmen Sandiego fit into the whole init system debacle?
Yeah, you’d have a LoadBalancer service for Traefik which gets assigned a VIP outside the cluster.