FreeBSD 15.0-RC1 is here for both ARM64 and AMD64! This update touches everything from pkgbase and VM images to cloud builds and container tooling, giving testers plenty to explore. An expedited RC2 is already planned because of a VM image issue, but RC1 still offers a solid look at where FreeBSD is heading.
The images alone show how wide the project’s reach has become. There are builds for amd64, armv7, aarch64 (including Raspberry Pi, Pine64 boards, and Rock64 systems), powerpc64, powerpc64le, and riscv64. Some ARM images even ship with default login credentials to help people without serial consoles get started faster, though those passwords should be changed immediately.
One of the bigger structural changes is pkgbase. FreeBSD now treats the base system as a proper repository defined in /etc/pkg/FreeBSD.conf, hosted at pkgbase.FreeBSD.org, and signed with its own keys. On paper it makes sense. In practice, some long time users still view the shift with caution because it changes how the operating system is organized at a fundamental level. Whether it becomes beloved or just tolerated remains to be seen.
There are also improvements tucked into the boot process, including support for dynamic gang headers. Plenty of bug fixes land here too, especially around networking and 32 bit compatibility. For people who still depend on older software or specialized hardware, those changes matter more than the flashy packaging updates.
Cloud support gets more attention this cycle. 15.0-RC1 ships with explicit build fixes for Google Cloud and Azure, and the team is continuing to publish Amazon EC2 AMIs for both amd64 and aarch64. It is interesting to see FreeBSD continue leaning into cloud images while Linux distributions dominate the space. Still, having FreeBSD as a first class citizen in AWS, Azure, and GCP expands its relevance in a world that is increasingly container and VM oriented.
The virtualization support is thorough as usual. VM images are available in QCOW2, VHD, VMDK, and raw formats, with a simple three partition layout that keeps things predictable. Aarch64 users running QEMU will need a modified EFI loader, which the project documents clearly, along with the exact qemu-system-aarch64 command to make it boot cleanly.
On the container front, FreeBSD continues to flesh out its OCI images. The team offers static, dynamic, runtime, notoolchain, and toolchain variants in multiple architectures. You can load them with Podman or push them to registries with skopeo. If you prefer convenience, amd64 and aarch64 users can pull from Docker Hub or GitHub Container Registry by tag. For people who blend Linux and BSD containers in the same environment, this makes FreeBSD far easier to drop into an existing workflow.
Upgrades follow the usual freebsd-update process. Systems on amd64, i386, and aarch64 can step through fetch, install, upgrade, reboot, and cleanup. For anyone jumping from something older like 12.x, rebuilding applications is still the recommended approach. Compat packages exist, but they are more of a temporary patch than a real solution.
What stands out the most in 15.0-RC1 is how the project balances tradition with modern expectations. It still feels like FreeBSD, but with enough cloud, container, and VM work to stay relevant alongside Linux distributions that have raced ahead in those areas. Some of these shifts may make purists uneasy, yet they also give FreeBSD a wider footprint at a time when operating systems either adapt or get ignored.
With RC2 on the way, this is a great moment for testers to jump in, file bugs, and shape the final 15.0 release. FreeBSD may not dominate headlines like Linux does, but RC1 shows a project that keeps moving, keeps modernizing, and refuses to fade into the background.
