After I learned that TrueNAS Core 12 went STABLE recently (I missed any official announcment regarding this here), I upgraded my FreeNAS-system running 11.3-U5 yesterday.
My system runs several jails with various functionality. I don't use plugins but build all my jails myself with scripts using the ports (BubbleUPnP, plex, dnsmasq, MinimServer, unison, transmission, nextcloud).
I can report that everything so far works fine without any action required from my side. All the jails still work and do their job, although they are still 11.3 based. I am wondering why this works, as others report that their jails stopped working. The only - expected - sideeffect is that the jails cannot be updated any more (make: "/usr/ports/Mk/bsd.port.mk" line 1204: UNAME_r (12.2-RC3) and OSVERSION (1103000) do not agree on major version number.
)
As I have scripted the creation and building of all these jails, there is an easy fix: I will just rebuild the jails one by one (I did this already in the past on main version upgrades). I saw that TrueNAS Core 12 offers two release-versions for creating new jails, 11.4 and 12.1.
When I type "uname" on the shell of the new TrueNAS-system, I see that it uses 12.2-RC3 as its OS. Why is then possible to chose between 11.4 and 12.1? Shouldn't it be just 12.2? I thought jails base on the same kernel and have to share the version number? I guess the best way to go forward now is to chose 12.1 as the base for the jails, although the host uses 12.2, right?
Kind Regards,
airflow