GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
APPJAIL-jail(1) FreeBSD General Commands Manual APPJAIL-jail(1)

appjail-jailCreates, removes, lists and configures jails

appjail jail boot [off|on] jail

appjail jail clean

appjail jail create [-a architecture] [-I install-method] [-i initscript] [-r release] [-T type] [-t template] [-v version] jail

appjail jail destroy [-fR] jail

appjail jail get [-eHIpt] jail [keyword ...]

appjail jail list [-eHIpt] [-j jail] [keyword ...]

appjail jail mark [clean|dirty] jail

appjail jail mark [locked|unlocked] jail

appjail jail priority -p priority jail

appjail jail rename jail new-name

The utility creates, removes, lists, configures or basically can manage many things related to jails and their properties. appjail-quick(1) uses it to create, remove, and mark them as dirty.

The options are as follows:

[off|on] jail
Enable (on) or disable (off) the boot flag for jail. If the boot flag is enabled, appjail-startup(1) will start and/or stop jail, a process commonly performed by the rc(8) script.
Remove dirty jails.
[-a architecture] [-I install-method] [-i initscript] [-r release] [-T type] [-t template] [-v version] jail
Create a new jail. This subcommand only has the responsibility of creating a jail; It is highly recommended to use appjail-quick(1) unless you know what you are doing.
architecture
Specify the architecture to use in the jail. If this option is not set, the architecture specified by the parameter is used.
install-method
Specify the installation method that affects the jail type and how you should use this subcommand. If this option is not set, the installation method specified by the parameter is used.

See INSTALLATION METHODS for a list of available installation methods.

initscript
to make the jail interactive.
release
Specify the release to use in the jail. If this option is not set, the release specified by the parameter is used.
type
Type on which the jail is based. The default is thin.
template
Template file. If not specified, the template file specified by the parameter is used.
version
Specify the version of the operating system to use in the jail. If this option is not set, the version specified by the parameter is used.
[-fR] jail
Destroy jail.

If jail is a container, it will be destroyed before the files are removed.

Forcibly unmount file system. Ignored when ZFS is not enabled.
Recursively destroy all dependents, including cloned file systems outside the target hierarchy. Ignored when ZFS is not enabled.
[-eHIpt] jail [keyword ...]
Get information about jail, that is, the keyword that represent the information to be obtained. Multiple keywords can be specified, which are displayed as a table-like interface in the order in which they are specified. If no keyword is specified, the defaults are status, name, type, version, ports and network_ip4.

See KEYWORDS for a list of available keywords.

Not required when using -p. The \t character is used to delimit columns, so as not to show strange values, this option shows instead of \t in the case that a value contains the latter.
Shows the name of the columns.
Include empty values. By default, a minus sign is displayed when a value is empty.
Columnate the list.
Tabulate columns and values.
[-eHIpt] [-j jail] [keyword ...]
get but shows each keyword for each jail in a nice table.
, -H, -I, -p, -t
get.
jail
jail.
[clean|dirty] jail
jail can be marked as dirty, which is something like an atomic operation. When a jail is marked dirty, appjail(1) and its subcommands are free to treat the target jail as incomplete and error-prone, so the behavior is typically to destroy it and start over, an operation commonly performed by appjail-jail(1), appjail-quick(1), the clean subcommand, and so on.
[locked|unlocked] jail
Used by appjail-start(1) to prevent another process from executing it (e.g.: the user spawns a new shell and executes appjail-start(1)) while the first one is still running.

Marking jail as locked locks it, but if you try to lock it again it fails unless it is marked as unlocked.

-p priority jail
Change the priority for jail.
jail new-name
Rename jail with a new name.

="jail@snapshot"

Create a new jail by cloning a ZFS snapshot of jail.

Parameters:

  • jail: Jail to create a ZFS snapshot for cloning.
  • snapshot: ZFS snapshot name.
="snapshot"

Create a new jail by cloning a ZFS snapshot of a release.

With this option only the linux+debootstrap and thick jail types can be used.

Parameters:

  • snapshot: ZFS snapshot name.
="jail"

Create a new jail by copying another existing jail.

Create an empty jail.

="output:outname [portable] [compress:algo]"

Export the jail directory to a tarball file.

Parameters:

="output:outname [portable] [compress:algo]"

Export the root directory of the jail to a tarball file.

Parameters:

  • : Output name.
  • Include only portable files, that is, the jail directory, the InitScript, the configuration file that describes the jail, and the specifications of volumes used by the jail. This is used by appjail-image(1).
  • : If specified, the file will be compressed.

    See COMPRESSION ALGORITHMS for a list of available compression algorithms.

="input:file [portable] [compress:algo]"

Create a new jail by importing a tarball file into the jail directory.

Parameters:

  • : Tarball file.
  • : Ignored, but used by import+root.
  • : Ignored, but used by zfs+import+jail and zfs+import+root.
="input:file [portable] [compress:algo]"

Create a new jail by importing a tarball file into the root directory of the jail.

Parameters:

  • : Tarball file.
  • : Include only portable files, that is, the jail directory, the InitScript, the configuration file that describes the jail, and the specifications of volumes used by the jail. This is used by appjail-image(1).
  • : Ignored, but used by zfs+import+root and zfs+import+root.

Create a thin, thick or linux+debootstrap jail.

="files:file output:outname [compress:algo]"

Export a jail directory with only the files needed to run a program.

Parameters:

  • : A file that contains a list of files to export.
  • : Output name.
  • : If specified, the file will be compressed.

    See COMPRESSION ALGORITHMS for a list of available compression algorithms.

="file"

Create a new jail by importing a TinyJail.

="output:outname [portable] [compress:algo]"

Recursively export the jail dataset to a ZFS image file.

="output:outname [portable] [compress:algo]"

Recursively export the root jail dataset to a ZFS image file.

="input:file [portable] [compress:algo]"

Create a new jail by importing a ZFS image into the jail directory.

Parameters:

  • : ZFS image.
  • : Ignored, but used by import+root.
  • : Change the compression algorithm. Automatic detection of the algorithm used by the ZFS image is performed, but if it fails or you need to change for some reason, you do so using this subparameter.
="input:file [portable] [compress:algo]"

Create a new jail by importing a ZFS image into the root directory of the jail.

Parameters:

  • : ZFS image.
  • : Ignored, but used by import+root.
  • : Change the compression algorithm. Automatic detection of the algorithm used by the ZFS image is performed, but if it fails or you need to change for some reason, you do so using this subparameter.

Displays the alternate DNS name.

See also appjail-network(1).

AppJail version that was used to first create the jail.
Architecture that was used at the creation time.
Shows 1 if the boot flag is enabled, 0 if it is not.
Displays the name of the container.
Displays 1 if the program defined in the OCI image is to be executed by appjail-start(1), 0 otherwise.
Displays the OCI image used to create the container.
Displays the PID of the program defined in the OCI image running in the background if it is running.
Creation date. The parameter specifies the format to display this value.
Shows the ruleset assigned by appjail-devfs(1).
Shows 1 if the jail is dirty, 0 if it is not.
Shows the hostname assigned by the parameter in a template.
Shows all IPv4 addresses reported by ifconfig(8). If the jail is not running, IPv4 addresses cannot be retrieved.
Same as inet but for IPv6.
Shows the IPv4 addresses assigned by the parameter in a template.
Same as ip4 but for IPv6.
Displays 1 if the jail is a container, 0 otherwise.
Shows 1 if the jail is locked, 0 if it is not.
Shows the jail name.
Shows all current IPv4 addresses assigned to the jail for all virtual networks it is on.
Shows all virtual networks the jail is on.
Jail directory.
Jail priority.
Exposed ports. Note that this does not mean that port forwarding is performed, it only shows the ports that are marked to be exposed and may or may not be currently forwarded.
Release that was or is currently being used by the jail.
Shows if the jail is currently started, if not.
Jail type.
Operating system version that was used at the creation time.
String commonly used when the jail was created using a build from the FreeBSD source tree.

 
 
.
 
 
.
 
 

The appjail jail utility exits 0 on success, and >0 if an error occurs.

appjail-expose(1) appjail-fetch(1) sysexits(3) appjail-initscript(5) appjail-template(5) appjail.conf(5)

Jesús Daniel Colmenares Oviedo <DtxdF@disroot.org>

April 4, 2024 FreeBSD 14.3-RELEASE

Search for    or go to Top of page |  Section 1 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.