MinIO Compatibility

Prepare legacy host and plugin MinIO deployments before upgrading to FreeCORE 15.0.

The built-in S3 service was deprecated in TrueNAS CORE 13.0 and its supported service interface is not present in FreeCORE. FreeCORE 15.0 also removes two unmaintained host packages:

• the MinIO server and its /usr/local/etc/rc.d/minio startup script; and
• the archived /usr/local/bin/minio-client administrative command.

The package-list change contains no intentional MinIO object-dataset cleanup, but it is not a data or configuration migration and does not guarantee that package-owned files survive. A manually enabled host server no longer starts, and shell scripts that invoke minio-client no longer find that command.

Before Upgrading

On the 13.3 system, check for a manually enabled or running host instance and for installed MinIO packages:

sysrc minio_enable
service minio status
pkg info minio minio-client

Also review local scripts and scheduled tasks for minio-client. Back up the object data, server configuration, credentials, and any application metadata needed to reproduce the deployment. Test a restore or migration before applying FreeCORE.

Existing MinIO Plugin Jails

The historical MinIO plugin is end of life and should not be used for a new deployment. FreeCORE does not delete an existing plugin jail during the upgrade, but it cannot make the unmaintained application inside that jail current or guarantee an automatic data migration. Keep an independent backup and plan to move the workload to a maintained deployment.

Replacement Boundaries

FreeCORE Cloud Sync continues to support S3-compatible storage through rclone and can cover ordinary object copy and synchronization workflows. It does not replace minio-client admin operations. Run administrative workflows from a maintained external client, and run an object server on a maintained external system, virtual machine, or operator-maintained jail appropriate to the deployment.