Bastille 0.14: FreeBSD Jail-Based Container Control

The latest release of BASTILLE 0.14.20250420 has been published, a system designed for automation of deployment and management of applications launched in containers isolated using the FreeBSD jail mechanism. The code is written in Shell, has no external dependencies, and is distributed under the BSD license.

BASTILLE provides a command line interface to control containers, allowing users to update Jail-delays based on the selected FreeBSD version. Users can also perform various operations such as launching/stopping containers, assembly, cloning, import/export, configuration changes, network access control, and resource consumption restrictions. More information can be found on the official documentation site.

BASTILLE supports deployment in the Container Circus C Linux (Ubuntu and Debian) using linuxulator. Advanced features include running commands in multiple containers, using templates, creating snapshots and backups, and mounting the root section of the container in read-only mode. The container environment can be set up on physical servers, Raspberry Pi boards, or cloud services such as AWS EC2, VULTR, and DIGITALOCEAN.

The repository offers approximately 80 templates for quick deployment of standard application containers, including servers, developers, and user applications. It also supports container nesting, allowing the use of one template within another.

In this new release, several features have been added to BASTILLE:

  • Added option “-c” (“–config”) and the environment variable Bastille_config for setting user configuration files.
  • Added Auto-Mode (“-a”, “–Auto”) for launching and stopping Jail-rings as needed.
  • Added Debug-Mode (“-x”, “-debug”) for infrastructure debugging.
  • Added the ability to add a delay before launching another Jail (e.g., when one Jail launches a DBMS used by other Jails).
  • Added support for multiple targeted environments in the “

/Reports, release notes, official announcements.