So for anyone finding this thread later, I was a bit reluctant to upgrade from 13.0-U6.2 to 13.3 due to the issue reported here around the daemon being broken.
However, I decided to do it as I will be away from my server for about 6 months and wanted to reduce the issues I may encounter while gone. I use several jails (Unifi Controller, Plex, Son/Rad/Lid-arr) and it was important for those to keep running and for me to have the ability to update them while away if needed.
I am also reluctant to move to TrueNAS Scale until the 24.10 release (because I use several jails and want to wait for the Docker support), but I will not be on-site so I will have to wait until spring '25 (at which point 25.04 will likely be available).
All that said, I did the upgrade Friday and then updated my jails to 13.3-RELEASE as well (using iocage upgrade -r 13.3-RELEASE [jail]). Everything seems to be working fine so far.
Yeah, that wasn’t totally clear to me based on this thread. It made it sound like 13.3 was broken, and that upgrading to 13.3 of TrueNAS wouldn’t fix it. I didn’t understand that the issue is running a 13.2 or 13.3 jail on a 13.0 TrueNAS Core.
I should expand on this since I had a negative experience:
If you upgraded (and broke) your jail’s daemon before upgrading to 13.3, you must recreate your jail.
In 13.3 the fix was to revert the daemon to before the change, so if you already upgraded the jail, upgrading truenas afterwards will not make the new “daemon” functional.