I’d say “usually” been possible.
While there is no “Train” for 13.3, updates do appear to be coming out if I’m reading things correctly.
It appears that a new build was posted yesterday, however no description of what was changed.
My Questions: How long will iXsystems continue to post updates? What is the criteria?
I’m just looking at this from an EOL perspective. I would not expect to see many significant changes from here forward but if someone is creating nightlies then something is warranting that work.
-Cheers
The gigs up. They’re on to us. Yes, we are planning on ditching SCALE and focusing all our efforts on CORE.
We have listened to all the hardcore BSD guys and have decided to go ahead and keep CORE going.
I got hit by this, which came about due to an update to Samba.
13.3-U1 on the Unreleased page, slated for 11th November…
It’s not a simple decision. We’d like to maintain a solid and secure product for 13.0 and 13.3. From this base, we want to provide easy and unrushed migration to 24.10 or later.
However, we are handcuffed by FreeBSD’s 13.3 process. So, fixes that are not dependent on the OS are easier. Jails and plugins and Bhyve fixes will be harder if not included in 13.3.
That is the plan. Dates can change.
So my advice would be:
- Report any major issues (or submit fixes)
- Plan to sidegrade if you need more than storage
- Identify what you need to sidegrade in 2025 and let us know
Our assumption is that a jails-like experience is required for many users to sidegrade.
In 24.04 we added Sandboxes and jailmaker. Coupled with Dockge its pretty powerful, but not as easy if many “jails” are needed.
In 24.10 we have Docker Compose. Its certainly a step in the right direction. Try out the BETA.
In 25.04 we plan to add Incus and LXC
Clearest endorsement so far for LXC.
Incidentally, what’s the code name for the ‘F’ fish? Flapping Flounder?
I propose Featherback or Fangtooth.
Nice proposal! It would not take much editing to turn an Anoplogaster (fangtooth) into the kind of dark fantasy artwork we’ve had for Dragonfish and Electric Eel…
There is the “TrueNAS-13.3-Nightlies” train, configurable via the command-line freenas-update
utility. I’m not suggesting anybody should use this.
It is Fangtooth. Check the nightlies…
Thank you for the answer. While I like my CORE system, I have also taken a look into SCALE 24.10.0 and am impressed.
Thanks for the feedback. We’d love to get constructive criticism on how we can improve given your specific use-case. Experienced users can see things we might miss.
FYI… its 24.10-BETA, so there will be a couple of additional improvements before RELEASE.
Or run thick jails, so there is a complete version of the OS inside the jail. I was happily running FreeBSD 13.3 thick jails on TrueNAS-13.0 before I upgrade to TrueNAS-13.3
Can you run a 14.x Thick Jail within TrueNAS 13.0?
What are the limits?
I no longer have a system running TrueNAS 13.0, so I cannot test this. But the very sparse info in the FreeBSD docs don’t suggest anything that would prevent a TrueNAS 13.0 system from running a 14.x thick jail.
You cannot. The 13.x kernel will not support 14.x binaries.
There is a good chance you will be able to run FreeBSD 13.4 and 13.5 binaries on TN CORE 13.3 but no guarantees. General policy is not to introduce breaking ABI changes during the life of a major version but as we saw with 13.2 → 13.3 occasionally they still happen.
The docs explicitly say this is unsupported. I wouldn’t expect it to work.
Thick or thin isn’t the issue, it’s about the impedance mismatch between the apps+libs in the jail vs. the kernel ABI.
Newer kernels almost always have explicit support compiled in for older userland. The opposite isn’t (can’t) be true.
Especially so across major versions. Which exist specifically to introduce breaking ABI changes.
As I argued above it is the general policy not to introduce them within a major version if it can be avoided so with a bit of luck we can hope for 13.4, 13.5, … jails working on TN CORE 13.3.
But again: no guarantees.
I didn’t have any issues running 13.2 and 13.3 jails in 13-U6.1. Anything changed that would prevent this in 13.3?