I think the dependencies might actually be a problem for the “one binary fits all” solution. For a simple binary the user is responsible for the external dependencies. If by any chance you’re using Arch, there a package in the AUR.

That’s actually not a bad idea. There are a few downsides to this like the binary being quite big compared to the classical “one binary per architecture” style. I’ll give it a though. The docker image is pretty small btw ;).

Sorry for the double response… I got an error the first time I hit Submit.

My favorite feature of good old reddit (rip)! Makes me feel right at home.

This is the way! There’s a catch with swap files on encrypted disks and hibernation but that’s quite a special case. Edit: forgot to mention zswap, the compressed version of swap.

I tried it a few times but was so slow (even in a local network), I ended up cancelling the transfer every single time. I prefer Syncthing which does require some basic setup though.

Not necessarily. For networking, I wrote a bash script with just a few lines that creates and assigns a private networking namespace to a pod and sets up the default routes. That script is run by a systemd user instance and has the suid flag set. One could argue that it’s not rootless because of that but that’s just the moment when it’s starting. No performance impact and very robust. A lot better than the docker network bridges imho.