| Port details on branch 2025Q4 |
- bastille Jail automation framework
- 1.2.2.251204 sysutils
 =0      1.2.2.251204Version of this port present on the latest quarterly branch. - Maintainer: jdhurtado@orbiware.com
- Port Added: 2025-10-02 11:03:06
- Last Update: 2025-12-04 19:07:09
- Commit Hash: 2f2b7bc
- License: BSD3CLAUSE
- WWW:
- https://bastillebsd.org
- Description:
- Bastille is an open-source system for automating deployment
and management of containerized applications on FreeBSD using
the jail framework.
The project focuses on secure defaults, automation and
repeatable templates.
  ¦  ¦  ¦  ¦ 
- Manual pages:
-
- pkg-plist: as obtained via:
make generate-plist - USE_RC_SUBR (Service Scripts)
- no SUBR information found for this port
- Dependency lines:
-
- bastille>0:sysutils/bastille
- To install the port:
- cd /usr/ports/sysutils/bastille/ && make install clean
- To add the package, run one of these commands:
- pkg install sysutils/bastille
- pkg install bastille
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: bastille
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1764866943
SHA256 (bastillebsd-bastille-1.2.2.251204_GH0.tar.gz) = f8bb0d02601648833a4563f7b324235c169dd6968037fd2b518d6d9b4645733e
SIZE (bastillebsd-bastille-1.2.2.251204_GH0.tar.gz) = 707979
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- This port has no dependencies.
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- sysutils_bastille
- pkg-message:
- If upgrading from > 0.13:
- **Breaking changes since 0.14.20250420**
The `rcorder` has been deprecated, and new `boot` and `priority` options have
been added to the jails. A boot file will be created with default values of
`boot=on` and `priority=99` on jail creation. For existing jails, the boot file
will be generated on the next subcommand execution to the jail. If you want to
generate the file for all the jails, you can use `bastille restart ALL` to fill
in the defaults. To change these values, use `bastille config TARGET set boot off`
or `bastille config TARGET set priority 10` or some other number according to
your needs.
- If upgrading from > 0.14:
- **Notice: Potencially breaking changes since 1.0.20250714**
Network: Bastille now handles all epairs dynamically, allowing both -V and -B
VNET jails to coexist. Previous versions only supported one type per system.
New naming scheme for network interfaces is e0a_jailname (host side) and
e0b_jailname (jail side). Additional interfaces: e1a_jailname, e1b_jailname, etc
(incrementing numbers). Long jail names are truncated with xx placeholder due to
interface name limitations
Required action after update:
Restart all jails (preferably one at a time) to trigger automatic conversion.
Bastille will auto-convert jail.conf and rc.conf files when jails are stopped.
Manual intervention required: If you previously used the network sub-command to
add interfaces, manually edit jail.conf and rc.conf files to update epair names
(increment numbers for additional interfaces).
Auto-conversion handles most cases, please report bugs if issues occur during the
transition.
Full release annoucement: https://github.com/BastilleBSD/bastille/releases/tag/1.0.20250714
- Master Sites:
|
As an Amazon Associate I earn from qualifying purchases.
