Home

Readme updated today:

This repository is no longer actively maintained.  

The TrueNAS build system previously hosted here has been moved to an internal infrastructure. This transition was necessary to meet new security requirements, including support for Secure Boot and related platform integrity features that require tighter control over the build and signing pipeline.  

No further updates, pull requests, or issues will be accepted. Existing content is preserved here for historical reference only.  

https://github.com/truenas/scale-build

Wondering if this is just the first step towards doing a minio in the future.

Always blaming security bullshit. I anxiously await a community fork.

Security through obscurity isn’t security.

There goes my excuse for not giving up and just paying for Unraid.

Odd choice of timing… I wonder if they are sitting on a cache of hard drives.

Truenas went to shit when they killed BSD support, the OS it was founded on

Volker Theile (lead dev of FreeNAS 2006-2009) maintaines OpenMediaVault, based on debian, version 8 was released recently. Not a drop in replacement, and it has its own quirks, but no evil company in the background

Postgres is used by highly secure environments and has a public build pipeline.

This is bullshit and/or they are lazy.

I found a post on the forum:

https://forums.truenas.com/t/scale-build-git-repo-going-closed-source/64313

This is only their old build system which they weren’t using themselves, the rest of the OS will remain open source. However they also said some worrying stuff about including “proprietary pieces of the OS”.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

[Thread #153 for this comm, first seen 10th Mar 2026, 00:40] [FAQ] [Full list] [Contact] [Source code]

Are they lying about secure boot being a reason or can I go back to thinking SB is part of Microsoft’s EEE attack on Linux?

I’m running an early version of that on a 16 year old ARM board NAS, the NAS has 256MB of RAM and OpenMediaVault runs great on it.

It can be a bit of both.

I don’t think secureboot is an attack on freedom exactly (and it’s certainly not an instance of EEE), but I definitely think it shouldn’t be Microsoft holding the keys.

@tabular @Ek-Hou-Van-Braai They are lying. Debian supports Secure Boot and remains open.

Unraid pay system switch made me never want to use them

TIL. Now it’s based on Debian.

I ordered a TrueNAS system from iXsystems a few years ago, and the reasoning they gave me is that Linux has better driver support, especially for home users who.

Whether that was actually the reason, I have no clue. But that’s what they said.

Literally today Chris Titus released a video where he emphasized that no one should be using secure boot because the default backend is Microsoft and no one changes their secure boot config.

If that’s true there’s an argument that the name “secure boot” is hardly detachable from the defaults and thus that name is kid of burnt and shouldn’t be recommended out of an abundance of caution for new users.

The reason they gave me is people can run apps with docker on Linux, and docker isn’t compatible with FreeBSD jails…

And yet they went with K3s at first, a crappy implementation at that, and refused to even consider adding Docker for like a year, then suddenly it became super important to replace their k3s stack with docker in the next release, barely giving people 2-3 months to get all their apps updated.

you can always just bypass their security.

Huh

Not only that but there wasn’t even a notification on the dashboard for me after updating the OS that k3s were being replaced, I found out after updating when my apps wouldn’t work. When did I update? About 2 weeks after the migration deadline. Had to rebuild my Plex, Jellyfin and Immich apps.

Don’t get me wrong, I don’t like notifications from the OS developer in my system, but that would’ve been a great heads up and a worthy exception. “Hey migrate your apps now or your shit will break” would’ve worked.

K3S sorta makes sense in an enterprise environment but for the small one box use case it’s overkill and a pain to work with for little extra gain.

They are very hostile to users and I moved to a pure FreeBSD self managed storage and deployment solution

In a years time will the public be able to build trueNAS for themselves without developing their own build tools?

If not then the TrueNAS is no longer Open Source as people can’t practically build it for themselves

I love it so much that I donaged twice to the project. There are also some easter-eggs hidden in the software, like quotes from Dune.

According to their own documentation: https://github.com/truenas/scale-build

The TrueNAS build system previously hosted here has been moved to an internal infrastructure.

This isn’t them stopping use of the build, it’s them making it proprietary. They are still using it, just not open-sourcing it.

Unraid uses a pretty whacky “license” checking system. There’s cracks for it out there that hook into the core license system and use it to generate a valid one for the current version.

One key note is that you HAVE to update the crack before updating Unraid itself.

And Unraid is OSS?
So my option are (potentially both) closed source storage software bjt one needs to be paid?

Well…I know what I’ll not choose.

Link to article?

Good bot

Looks like no zfs support?

I question why this gets recommended so much when we discuss truenas.

Without a doubt zfs is one of if not THE reason to go truenas. It does so much more for you than other filesystems.

I guess OMV at least has btrfs but not the same thing.

Do you know the name of this video? I keep trying to search for a secure boot video by Chris Titus released today/yesterday but I’m not finding anything.

I have it on my installation, you’ve got to replace the kernel with the proxmox one, it’s fairly easily done by installing a plugin

So glad I went with OpenMediaVault so many years ago

Why are they always coming up with some kind of bullshit excuse? :D

So… nobody changes the default settings, therefore everyone should change the default settings… to the wrong option?

Since omv 7 it works with the default kernel, you can install the proxmox lne though if you want that.

Oh so they are going to use the Puppet excuse to move away from open source?

we must move to have our code internal only for now. Totally just for security reasons nothing to do with us also changing licensing to make it harder for those building things for us

no don’t bring up the security incident we’re referring to that shows us as the issue not having code visible! (ie they cheaped out on people/set up and vendor had keys visible)

It’s not in their by default, you have to install the omv extras plugin, from there you can install zfs: https://wiki.omv-extras.org/doku.php?id=omv8%3Aomv8_plugins%3Azfs

ZFS is in the omv extras repo: https://wiki.omv-extras.org/doku.php?id=omv8%3Aomv8_plugins%3Azfs

As it’s just plain debian under the hood you can use any basic debian stuff, e.g. I use zfs-auto-snapshot from apt, and the zfs plugin can list and manage the snapshots perfectly.

It was in his reaction video to LTT trying it Linux again

Been running my own storage boxes off of rocky for years simply for the ease of integration of samba + freeipa.

Especially being able to use ipasam.so to allow password authentication for shares on machines that aren’t easy/reasonable to use kerberos keytabs from (think android clients, and off domain boxes)

Weird, some time ago it booted with the default kernel by mistake and it couldn’t see my zfs pool

There’s a link to the github page that has the depreciation notice right there..?

Damn man. Technology kinda fucking sucks now. Everything I use is imploding in on itself. Yay!

Uggh, I just got to the point where I’m as familiar with TrueNAS as my old Synology, but I want to move towards more freedom. TrueNAS beats Synology, but where is this going?

From the docs:

The Standard Debian Kernel (selectable) can be used for ZFS. However, since ZFS kernel modules are not installed in the Debian kernel by default, they must be built by the ZFS plugin when it is installed. While this process works, building the modules is a long process that requires continuous access to online repos. Accordingly, the potential for a build error exists. For this reason, while the Standard Kernel is very usable for ZFS, it is not ideal.

Ahhh that is good to know. Thank you.

yeah that’s the one

Not Proxmox! Use it for free at home, but buy it for your business if you can! (But they never force you to)

/hoping it doesn’t bite the dust too