It doesn't look like there are any third-party libraries, so running this in a VM or a container will be unavoidable. This does include a CLI, so you'll be able

It doesn't look like there are any third-party libraries, so running this in a VM or a container will be unavoidable. This does include a CLI, so you'll be able to service some use cases without launching the GUI. If your frequency of usage is only once every few months, then create a VM, install the minimum version of the OS (Linux is pretty small) and maybe experiment with how much you can reduce the RAM usage. Once you've used the VM, compress it into an xz archive and put it on a shelf somewhere - whether it's a cloud drive, a USB thumb drive, or whatever. When you need it again, restore the image, do whatever you need, and put it back on the shelf when you're done. Ultimately, any "clever" solution is gonna go to waste, especially because you need to spend time to come up with a solution. Is your time something you want to give to Keybase? If not, then suck up the cost of maybe 30 gigs worth of storage off in a corner of your SSD/office desk, and maybe a few times of discomfort a year when you need to run with a reduced amount of RAM. It's a small amount of resources compared to your time, and doing it by brute force is cheap these days.