Testers,
Our first set of Nightly images for what will eventually become TrueNAS 25.04, with the latest Linux 6.12 kernel have been built:
Manual Update File:
https://update.sys.truenas.net/scale/TrueNAS-SCALE-Fangtooth-Nightlies/TrueNAS-SCALE-25.04.0-MASTER-20241125-005540.update
As usual, these are intended for developer and tester types only. Don’t use with production data, things may be unstable or otherwise broken in a variety of ways. 
Upgraded one of my backup systems, so far 6.12 seems to be humming along fine:
Good chance to play with the new containers WIP feature as well. So many distros to pick from, its almost overwhelming. I’ve always wanted to try Arch… 
Before someone asks, cloud variant of image is variant with cloud-init enabled: How to use cloud-init - Incus documentation
That’s my plan, if I eventually migrate to SCALE and switch over my FreeBSD jails to Linux “Incus” jails.[1]
The Arch rolling release model + the AUR + a legit filesystem to do custom things
=
Very similar to a FreeBSD jail + the pkg repository on the latest branch
I already use Arch-based distros as my daily desktop, anyways.
This assumes that the Incus method on SCALE allows for the same, no-nonsense management: unambiguous mountpoints; a complete network stack that does not share the host’s IP address; no dependence on any other “hidden” or “iX” datasets, other than a “jails” family of datasets, a la iocage. It would also be nice to set the compression level in advance, before an “Incus jail” is created. (Using ZSTD-9 on my iocage datasets, before a jail is created, is very effective. Root filesystems compress very nicely.) ↩︎
Why assume when you can test? Any issues found early have a chance of resolution without waiting 6 more months.
I will note, the implementation is only partial right now, but either way, early feedback during active development is always encouraged!
The bridged network mode isn’t enabled in the UI yet, just NAT / Port Forwarding. But that is expected to land soonish, we’re still in the early days of the dev cycle for Fangtooth.
The naming is going to cause troubles. I can already the “it’s getting long in the tooth, with Fangtooth” jokes
That’s OK, by the time you are good and sick of those jokes, the Goldeye release will be out and we can tell folks to upgrade 
Goldeye? I cant help but call it GoldenEye.
…which will be about the time when Betta Halfmoon goes alpha and the Hell of Name Jokes will break loose.
