Jurgen Segaert
Guru
- Joined
- Jul 10, 2016
- Messages
- 521
The original posting was made when jails in FreeNAS were managed by warden and as of FreeNAS 11.3, jails are managed using iocage. That being said, the package list and build instructions are still the same.
The only differences would be step #1 and step #6.
Creating a jail in the UI looks very different from how it looked in the pre-11.3 UI. All jail networking options (Shared IP, VNET, DHCP or NAT) should work with MineOS, but if you chose to use NAT you'll have to forward port 8443 and 25565 (or whatever ports you have your minecraft servers listen on).
There's an option/checkbox in iocage that automatically mounts
The new iocage plugin is trouble free under FreeNAS 11.3. The only difference is that the plugin script uses a proper rc.d script instead of using the supervisord service.
The only differences would be step #1 and step #6.
Creating a jail in the UI looks very different from how it looked in the pre-11.3 UI. All jail networking options (Shared IP, VNET, DHCP or NAT) should work with MineOS, but if you chose to use NAT you'll have to forward port 8443 and 25565 (or whatever ports you have your minecraft servers listen on).
There's an option/checkbox in iocage that automatically mounts
lincprofs
upon startup, so that eliminates step #6.The new iocage plugin is trouble free under FreeNAS 11.3. The only difference is that the plugin script uses a proper rc.d script instead of using the supervisord service.