Download¶
BSDnas v0.1.4-dev — installable ISO, 1.3 GB, built 7 October 2026.
Development build
This is a development build. It has been verified on one virtual test machine and one physical machine (a desktop board with four SATA disks) — no varied controllers, no real workloads. Treat it accordingly: do not put your only copy of anything on it, and keep a configuration backup.
Verify what you downloaded¶
The release includes SHA256SUMS and a detached OpenPGP signature over it.
Checking the checksum alone only tells you the download is not corrupted —
anyone able to replace the image can replace the checksum file too. Check the
signature as well.
gpg --import BSDnas-signing-key.asc
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c SHA256SUMS
Expected: a good signature from BSDnas release signing <bsd@22r.tech>, then
BSDnas-15-MASTER-202610071727-3d8df4ab98.iso: OK.
Signing key fingerprint — compare it with the copy on this page, which is served over a different path than the release itself:
5852 8D1C DBDA AF7B 01ED 2BBE 1E2F 7A79 2066 322D
The key is also available here: BSDnas-signing-key.asc.
The secret key is kept offline by the maintainer — it is not stored in any project repository or on any project server, and its handling is not documented further, deliberately.
What is in this build¶
| base | FreeBSD stable/15 |
| OpenZFS | 2.4.3 |
| Samba | 4.23 |
| ports tree | FreeBSD quarterly 2026Q2 |
| containers | podman, ocijail, CNI plugins included |
Next steps¶
- Installing — fresh installation
- Upgrading from TrueNAS CORE — read the
zpool upgradesection before you upgrade a pool - Containers — running FreeBSD and Linux images
- Project status — what is done, what is not, what was never tested
Newer builds arrive without a download¶
The ISO on this page is a fixed point in time. Once the system is installed it
tracks the project's update train and can update itself — System → Update in
the web interface, or midclt call -job update.update '{"reboot": true}' from
the shell. No media, no second download.
The train usually carries a newer build than the ISO published here, because the ISO is only refreshed for milestones.
Older builds¶
Superseded development builds are removed; the update train carries systems forward, so old ISOs only accumulate risk.