> but has had zfs issues for me.
Can you give more details so I know what to watch out for? (Recently started running Docker+ZFS in prod, haven't seen it break yet but appreciate heads up)
Can you give more details so I know what to watch out for? (Recently started running Docker+ZFS in prod, haven't seen it break yet but appreciate heads up)
More worryingly, 'prune' locked up for about 10 minutes before getting to do it's thing. pinning the cpu the whole time. This was on my devbox, so maybe it's my doing but did not inspire confidence.
I've run FreeBSD ZFS for about a decade and openzfs/ubuntu in prod for kafka clusters so I'm no stranger - this docker usage was just particularly strange.
It might actually have been this ms sql issue that led me to do that, actually:
I have to run snapd on one of my servers and I hate everything about it.
Am I in for a world of hurt?
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.
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.