5 ms·

I am pretty sure Canonical will soon release a stable,production ready snap package for zfs.

• alyandon 5y ago
  That gets updated arbitrarily at random intervals (because who doesn't want filesystem modules updated frequently!?!?!) and then purges logs every 72 hours so when you have a problem you'll never even know what was updated! I have to run snapd on one of my servers and I hate everything about it.
  • flemhans 5y ago
    I'm considering to run lxd as a snap because I want Debian 11 (for openzfs 2.0) and lxd at the same time. Am I in for a world of hurt?
    • alyandon 5y ago
      I wouldn't say you are in for a world of hurt but you'll have to accept that the package will periodically update and in the process kill your containers/vms. My primary objections to snapd are: 1) updates are pushed/applied and services restarted on an arbitrary schedule which means you can't test updates prior to rolling them out or otherwise control when a service is taken offline by an update 2) snapd doesn't log to standard OS logging facilities and the logs it does have are cleared after 72 hours 3) snapd pollutes home directories with a directory called "snap" snapd is a poorly conceived project written by people that are profoundly ignorant of how real services and servers are actually operated. Despite having the above flaws repeatedly pointed out, the developers have shown zero interest in taking actual concrete actions to address them.
      • flemhans 5y ago
        Thank you for the reply. It seems snapd is indeed a poorly conceived project. How would you work around it in a production setting if you HAD to use it? Auto-updating sounds like the biggest issue of those.
        • zekrioca 5y ago
          Build LXD yourself. It is not that complicated if one updates go to something beyond 1.14. Only downside is that you may need to create your own init scripts and a lxd group, but that's not complicated either.