zrepl VS Moby

Lastly there is zrepl. This is an automatic snapshot creation, pruning and replication daemon. It lets you automate the creation of ZFS snapshots at specific intervals, apply a retention policy to them, and replicate them out to a remote system with ZFS, like a NAS with TrueNAS on it.

I run it in a FreeBSD jail and take frequent ZFS snapshots using zrepl. I’ve had to restore after failed updates and it worked flawlessly.

As others have noted, I use syncoid but zrepl is an alternative that could be considered.

I’m going to throw out Zrepl again because it’s amazing: https://zrepl.github.io/

Current idea: We offer some form of container each other, where we have that zvol mounted somewhere for the replication use. This would mean that I could create an "inside zfs" where I create a filebased zpool. How is performance on a filebased zpool? (Although it is technically not so important that it performs critically, just trying to find the - or one of - "best" ways). Then we would offer each an ssh endpoint into that container (It doesn't have to be ssh, but it is so far convenient to setup and resilient to be open to the public). And my current plan is to use zrepl (https://zrepl.github.io/) to organise replication from my home server to this "inside" zpool.

Having been featured in our February 2023, and January 2024 Release Radars, Moby is the original Linux Container runtime. This new version adds a bunch of changes to the Docker CLI and Moby itself with additional features. There's bug fixes and enhancements, with the main thing for users to be on the look out for containers that were created using Docker Engine 25.0.0. These containers might have duplicate MAC addresses, and thus must be recreated. The same goes for those containers created with Moby 25.0+ and with user defined MAC addresses. Read up on all these changes in the release notes.

Formlabs does this as well for their 3d printers, my earliest encounter of this was when Docker started getting popular: https://github.com/moby/moby/blob/master/pkg/namesgenerator/...

Try to use moby instead since that is the engine in Docker.

https://github.com/moby/moby

> Podman is designed to help with this by providing stronger default security settings compared to Docker. Features like rootless containers, user namespaces, and seccomp profiles, while available in Docker, aren't enabled by default and often require extra setup.

Seccomp has been enabled by default since 2015: https://github.com/moby/moby/pull/18780

It is true that Rootless isn't enabled by default but its "extra setup" can be done with a single command (`dockerd-rootless-setuptool.sh install`)

Perhaps.

Thing is, https://github.com/moby/moby/blob/670bc0a46c4ca03b75f1e72f73... is using https://github.com/mistifyio/go-zfs which features code like `out, err := zfsOutput("get", "-H", key, d.Name)` (Source: https://github.com/mistifyio/go-zfs/blob/master/zfs.go#L315) to get a single zfs property.

Somebody chose to use a library as abstraction that looks good but is implemented as a MVP (nothing wrong with that). "In the future, we hope to work directly with libzfs" should have raised an alarm somewhere, though.

AppArmor can restrict /proc and this is even used by docker: https://github.com/moby/moby/blob/master/contrib/apparmor/te...