Opinion wise: love unifi for networking equipment. Especially since that equipment doesn’t require the web account. For a Nas, I’m in too deep already, I’ll only use equipment I fully control. I wouldn’t buy a Unifi NAS just like I wouldn’t buy a Synology, but I’ll keep leaning on my Unifi stuff as long as it keeps doing its job well.

As for using TrueNAS w/ZFS at home, go for it if you know and like it! I actually was recently given my boss’s old home NAS that used to run his Plex server. When I got it it was still on FreeNAS (same thing, just a few versions behind) and it’s using ZFS. Worked for him, and now works for me, no problem. Both of us also use Unifi equipment for our networks. The only problems we’ve ever had were our own doings.

Here’s the method I used from one of the issues on GitHub https://github.com/portainer/portainer/issues/12925#issuecomment-3516549977

Iirc my docker.socket wouldn’t let me just stop docker.service to edit it as described in the post, so I made /etc/systemd/system/docker.service.d/override.conf with the 2 required lines. After saving it and running daemon-reload I was able to access my containers in portainer again.

You can also add an override for the docker.service file to specify min api version 1.24. Had to do that last night