cross-posted from: https://lemmy.cloudhub.social/post/347779
I am running a Kubernetes cluster for this domain, and I’m looking at more services to run (right now I have Mastodon and Lemmy).
I was considering WriteFreely and PixelFed, but they don’t seem to have an easy solution for running on Kubernetes (WriteFreely doesn’t even have a production-ready docker image).
Is anyone else running federated services in their lab? Do you run any of them on Kubernetes?
I’ve done… an annoying amount of them now. I hope my trials help you.
Be ready, it’s a very annoying and slow process, watching logs, figuring out why things are failing, debugging, githubs, everything. I just did one last week that was saying that it couldn’t write to /etc/passXXXXX, and it took 2 hours to track down that there was an optional command I could pass in that would change the running user of the container I was running (separate from the kube user). It’s a slog, but when you get it running it’s a rush of endorphins.
Biggest thing - kubernetes is a read-only file system compared to docker. So, for good devs they minimize writes to the filesystem unless they have to, and keep them localized. For bad devs, they write everywhere - and that gets sticky fast. So, if you’re getting write errors, know that there’s probably another volume you need to attach. The kicker is knowing which ones can be an
emptyDirscratch directory and which ones actually need to persist. If you have adocker-composefile it’s a great place to start, just set all the volumes toemptyDirto start off with.Good luck!
I think both of the ones I mentioned have
docker-composefiles, which I think I can convert withkompose convert? I guess from there I would follow your steps and then start parameterizing it once it’s running properly.Thanks! I think I’ll start trying out PixelFed tomorrow.