FreeCORE Home Install Demo Documentation

Applications Screen

Reference for the catalog, the settings, the install, import, convert and export panels and the installed application actions in FreeCORE 15.1.

Applications is available in FreeCORE 15.1. The screen has Catalog and Installed tabs and an Applications Settings button in the page header. On the Catalog tab, the review, import, convert and export panels open under the catalog strip. See Installing and Managing Applications for a complete installation procedure.

Applications Settings

Setting Description
Data Pool Healthy, online, unlocked pool for the runtime and app-owned storage. Changing it selects another store; it does not migrate or delete the previous store. Running applications or installed records with external dataset references prevent a pool change.
Managed Container Subnet Private IPv4 network for the Applications bridge. Defaults to 10.88.0.0/16. It must not overlap the host's networks or routes. A change is refused while installed applications keep a fixed address on the bridge.
Convert & Import (experimental) Off by default. Required to plan and run a conversion from Convert jail… or the Jails page's Convert to application, and shows Export for Linux on installed applications. See Convert & Import.
Linux binary compatibility (experimental) Off by default. Loads the FreeBSD Linux ABI for the whole host so Linux images can be imported as applications. Every jail on the host can then execute Linux binaries. Best effort; no compatibility promise. Cannot be turned off while a Linux application is installed; loaded modules stay until the next reboot.
Unconfigure Applications Shown once Applications is configured. Stops the runtime and returns the settings to their defaults. Remove the installed applications is required while any are installed. Keep the store's data on the pool, selected by default, leaves the store and app-owned data on the pool for a later configuration of the same pool; clear it to destroy them.

Catalog and Review

The Catalog row names the catalog, Daemonless, with a link to its source. Update Catalog reads the current Daemonless catalog after a confirmation that states FreeCORE does not review the images. A provider or availability error is shown on the page. Import image… opens the import form described below. Convert jail… opens the conversion panel described in Convert & Import.

Filter applications searches the catalog; Category limits the strip. The strip shows each application as a tile with its icon; the arrows page through it. A tile marked Unavailable gives its reason in its tooltip and in the review panel. Select a tile to open its review panel.

Review section Description
Source, Support, Upstream, SBOM Provider attribution, support ownership, the upstream project and the provider's software bill of materials for the image.
Version, Architecture, Operating system The version of the image the catalog's tag currently resolves to, as the image states it, and the image platform. When the registry cannot be reached the row shows the provider's index instead and says so. The catalog uses native FreeBSD images.
Catalog copy Shown when the entry comes from the copy shipped with the image (seed shipped with the image) rather than a live read.
Tag, Immutable image, Digest The image reference the catalog follows and, when the registry answered during review, the digest it currently resolves to. Installation pulls the tag and records the digest it received.
Ports Host-to-container mappings and protocols.
Volumes Mount locations and whether the container receives read-only or writable access.
Environment Declared application settings and required values. Sensitive fields use password inputs.
Jail properties Additional properties requested by the image's configuration.
Startup check / Portal Declared HTTP startup-validation endpoint and web interface, when the application provides them. The startup check runs while the application starts; it is separate from the runtime health shown for an installed container.

Installation Fields

Field Description
Application name Unique name of 1–63 lowercase letters, digits, periods, underscores or hyphens, beginning with a letter or digit.
Restart policy Always, On failure, or Do not restart automatically. Only Always selects automatic startup after a host boot.
Network: Mode Applications bridge (default): the application joins the managed bridge and is reached through its published host ports. Attach to LAN: the application gets its own IPv4 address on the chosen interface; nothing is published through the host. See Applications Networking.
Interface, IPv4 address, Gateway Shown for Attach to LAN. The host interface whose bridge the application joins, a static address with its prefix outside the DHCP pool of that network, and the gateway of that network.
Also reach the Applications bridge Shown for Attach to LAN. Adds a second address on the Applications bridge, assigned automatically.
Environment Values exposed by this catalog entry. Review application-specific user/group IDs and any required credentials.
Host port Unused host port from 1 through 65535. The container port and TCP/UDP protocol are fixed by the entry. Management ports and conflicting mappings are refused. With Attach to LAN the section is named Ports and lists the container ports without host ports.
External dataset (optional) Existing dataset for that volume. Leave blank to create app-owned storage. Enter a dataset name, such as tank/app-data/homepage, rather than a filesystem path.
Applications Setup Pool and subnet selection shown during the first install if Applications has not been configured.
Confirm settings Confirms that the displayed settings have been reviewed before Install is enabled.

External storage must be an eligible, mounted dataset below a pool root. It can be on another available pool. The pool root and the managed Applications, Bastille and iocage stores are not external application-data choices. The mount's target and read-only mode come from the catalog; the field does not accept arbitrary container paths.

Edit opens the same form for an installed catalog application, titled Edit with its name. The name cannot be changed, environment values are not shown (an empty field keeps the installed value), each volume states what its change means for the app-owned dataset behind it, and the button reads Apply.

Import Image Form

Field Description
Compose file (optional) A raw.githubusercontent.com URL or the pasted YAML of one service. Read compose file fills in the form, carries the file's ports, environment and volumes, and lists what it ignored.
Image reference Any image reference, for example registry.example.org/team/app:1.4. It is pulled as given; the digest it resolved to is recorded.
Operating system FreeBSD native, or Linux (experimental, requires the Linux setting). The Linux choice is refused inline while Linux binary compatibility is off.
Application name Same rules as a catalog install.
Restart policy Same choices as a catalog install.
Host port (optional), Container port (tcp) One optional published port.
Acknowledgement Required: This image is not reviewed by FreeCORE. I own its supply chain from now on.

Installed Applications

Each row shows the application's Name, State and Restart policy. State reads up or down; for an application that declares a health check, a mark beside it shows the runtime health (Healthy, Unhealthy, Starting or Unknown). Unknown means no runtime result is available and can appear after a successful startup check. The row's expander shows:

Detail Description
Image The image the container runs.
Network Applications bridge with the application's address on the bridge, or LAN with its LAN address and interface, and its bridge address when it also reaches the bridge.
Source Catalog with the entry, Unreviewed with the image reference for an imported image, or Converted for an application made by Convert & Import.
OS FreeBSD, or Linux · experimental for an image running under Linux binary compatibility.
Action Result
Refresh Reloads the installed records and runtime state.
Edit Catalog applications only. Reopens the review form with the installed network, ports, storage mappings and restart policy, and replaces the container with the new settings and the image it already has.
Start, Stop, Restart Controls the existing container. These actions do not remove its persistent datasets.
Update Catalog applications only. Reviews the version the catalog's tag currently resolves to and replaces the container after confirmation.
Recreate Catalog applications only. Replaces the container with the current catalog contract. A newer available version must be reviewed through Update first.
Shell Opens a terminal inside the running container. Only shown while the application is running.
Logs Shows available container output. This is separate from an installation or replacement job's error.
Open Portal Opens the declared web interface: on the published host port, or on the application's own address for a LAN attachment. Only shown when a portal is defined.
Export for Linux Only shown while Convert & Import (experimental) is on. Opens the export panel described in Convert & Import.
Delete Deletes the application. Delete app-owned datasets also deletes its owned storage; the dialog lists the datasets it keeps or deletes. External datasets are preserved.

Orphaned app data, at the end of the tab, lists app-owned datasets that no installed application maps, with their size. Delete orphaned data destroys them after a confirmation that names each one. An application installed under the same name reuses its data instead.

Update and recreation retain saved settings and storage mappings. They may change application data, so container rollback is not a substitute for a data backup. Controls are disabled while an operation is active or when the required runtime or catalog state is unavailable.