(i forgot where i found this)

i’ll flush it down to them

This isn’t even lies, damned lies, and statistics territory - it’s just nothing. I know VR motion sickness exists (I still get it even after an uncomfortable amount of time in SteamVR sometimes) but that’s… that’s not anything

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.

They’re so close…

👋 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?