to appear to the rpi as a natively formatted partition (onto which that can be overlayfs).
Then perhaps the thing to do is back the iscsi lun on the fileserver as a zfs block device for the actual docker containers. This way, you even cut the network cable (so long as you don’t use PoE obviously) and you can eliminate network read/writes, you don’t need to have your / partition mounted on a NFS server. It doesn’t have to be on the SD card, you can boot a completely generic Alpine image via PXE and have Alpine get its own tar.gz archive to extract on its RAM FS.
What lbu commit does is creating a tar archive on whatever mount point you give it. That way, I get basically 0 read or writes on the SD card besides when doing an update and a lbu commit.
I can then install whatever crap I want, but after a reboot, it will revert to the previous state from the last commit and not have anything else installed, as those were only installed in RAM and not committed to disk. Whenever I do updates, I just do a lbu commit and the directories I have set to get backed up are stored on the SD card. I’m running Alpine on my pi 3 from an ancient 2 GB microSD card. If you want, you can unplug the SD card after the boot is over and it will be fine, so long as you don’t have any partition from the SD still mounted (only for safety of the SD, the system will still be fine without it, even forcefully unplugged). Heck, even with maintaining a bunch of SD cards, Alpine Linux on the Pi is running by default in Diskless Mode (“frugal mode”), which reads the image from an SD card (or storage of choice) and then loads the whole system onto RAM. But, for the Pi, especially if you run one with <2GB of RAM, I would highly recommend Alpine if it fits your needs. And Void has a lot of packages in the repo. Yeah, the inclusion of pi 4 images is nice, I still have my original self-compiled image running and it’s still going strong.
0 kommentar(er)
