magus
When a (typical) Linux system boots up, it first goes through an “early boot” environment that just has some basic drivers and things. The entire purpose of this environment is to find where your actual root file system is (which could theoretically be on something quite complicated, like RAID or a network file system), mount that, and then transition to the “real” system.
That error appears when something goes wrong with mounting the real file system.
👋 I’m not using Kustomize, just throwing Deployment manifests and such at the cluster manually. Works pretty nicely, though I had some trouble setting up the custom nginx stuff to proxy stuff in - I ended up running a new nginx instance and pointing the Ingress at that rather than the Lemmy pods directly. Maybe there’s a more elegant solution I’m missing?
- get on federated thing
- use corporate brand recognition and raw capital to get lots of users onto your instance of the federated thing
- lots and lots and lots of users
- “realize” that most of your users are only talking to each other, and maybe less than 10% is happening over federation
- (of course they are, you deployed all those resources to get as many users as possible)
- feel free to make things hard for the rest of the network along the way by being generally unstable for federated instances, since you represent such a huge number of users the rest of the network will cater to your broken nonsense
- leave federated network, citing “technical challenges” and aforementioned mostly-local-posting, causing everyone not on your instance to just mysteriously stop posting from the perspective of most users who aren’t keeping up with what seems like a bunch of nerd drama
this is, in essence, what happened to XMPP with Google