FreeCORE Home Install Demo Documentation

Bastille Screens

Reference for the read-only Bastille Jails list, the Releases view and Bastille Settings in FreeCORE 15.1.

Open Jails, then the cogwheel, then Bastille Jails. From 15.1-RC3 the screen is read-only: jails are created and managed on the console with the bastille command, and the interface shows what exists. See Bastille Jails for the console procedure.

The cogwheel on this screen offers Bastille Settings and iocage Jails. The toolbar offers Refresh and Releases.

Bastille Jails

Column Description
Name The jail's name.
State Running, Stopped or Unknown, with the reason when the state could not be read. Running jails are listed first.
IPv4 The jail's address. A running VNET jail shows the addresses it holds, including a DHCP lease; a stopped DHCP jail shows DHCP.
Release The FreeBSD base the jail runs on.
Auto-start Whether the jail is marked for automatic startup (bastille config <jail> set boot on). Both this and the service's Start Automatically are required for startup after a host boot.
CPU, Memory, Processes Live use by a running jail, from the same source as the dashboard Guests card. Shown as — for a stopped jail.
Disk Space used by the jail's dataset.
IPv6, JID, Path, Interface Additional columns, hidden by default.
Action Description
Console Log Shows the jail's console output, with a notice when only the last 64 KiB is shown.
Refresh Reads the jail list again, for example after a change made on the console.
Releases Opens the Releases view.

Releases

Column Description
Release A downloaded FreeBSD base.
Used Space used by the release.
Cache Space used by the release's download cache.
Jails The jails built on the release, or — when none.

Releases are downloaded with bastille bootstrap <release> and removed with bastille destroy <release>, which is refused while a jail uses the release.

Bastille Settings

Control Description
Data Pool Healthy, online, unlocked pool used by the Bastille store.
Startup Delay (seconds) Delay for automatic startup, from 0 through 3600.
Parallel Start Limit Maximum concurrent starts, from 1 through 64.

Once a pool is configured the dialog names the Bastille data location. The bastille command finds the configured pool on its own; no environment variable is needed.