• 1 Post
  • 144 Comments
Joined 1 year ago
cake
Cake day: December 28th, 2023

help-circle









  • I docker’d all of my systems a few years ago, and I’m so glad I did. So much easier to manage, and when I lost a system I was able to get most of my services back up and running with minimal configuration on a VM same day.

    As for hardware, you might check and see if you’ve got a local reseller of retired business equipment. Before I moved, I had a place I went to from my work that accepted shit we were getting rid of that disposed of stuff and resold at a bargain the stuff that was still good. I got more than one hp tower from a few years previous that ran (and still runs) like a champ. Felt like night and day when I upgraded to that from my Pi setup, and they were only like $35 each.



  • I might be able to hook it up to a usb NVMe reader, but when I initially tried I barely got any recognition of the drive from the OS. My primary system is windows, so I might get more info from one of my linux systems, just haven’t had the fucks to give to the dead drive. As for a replacement drive, funds are scarce and time/learning is (comparatively) free. Someone else suggested kubernetes, so I might look into that to see if that can accomplish what I’m looking for.





  • I’m actually not 100% what killed the drive. It could have been an issue with the drive wearing out, but my services didn’t write much locally and it wasn’t super old so I assume its a heat issue with a fanless micro system. I try to write everything important to my NASs so I don’t have to worry about random hardware failures, but this one didn’t have backups configured before it failed. Other than the drive issue its been solid for 1.5-2 years of near constant uptime.


  • So I amend to you don’t need it to be stateful, you could have an image like you talked about that is loaded every time (that’s essentially what kubernetes does), but you will still need space somewhere as scratch drive. A place docker will places images and temporary file systems while it’s running.

    Putting the image somewhere is easy. I’ve got TBs of space available on my NAS drives, especially right now with not acquiring any additional linux ISOs.

    For state, check out docker’s volume backings here: https://docs.docker.com/engine/storage/volumes/. You could use nfs to another server as an example for your volumes. Your volumes would never need to be on your “app server”, but instead could be loaded via nfs from your storage server.

    I’ll check that out. If that allows me to actually write databases to disk on the nfs backing volume, that would be amazing. That’s the biggest issue I run into (regularly).

    This is all nearing into kubernetes territory though. If you’re thinking about netboot and automatically starting containers, and handling stateless volumes and storing volumes in a way that are synced with a storage server… it might be time for kubernetes.

    I don’t think I’ve ever looked into kubernetes. I’ll have to look into that at some point… Any good beginner resources?





  • It doesn’t though. Whether they physically block you from getting care or put up financial blocks that they know will do the same, the outcome is the same and these layers of abstraction exist to make people like you ok with social murder.

    The fact that your argument is based around it being somehow not murder when they implement policies they know will lead to death by not doing their one fucking job makes me so fucking sad.