appjail-pkg
—
Manipulate packages within a jail
appjail pkg |
all [-e ]
[-i file]
target [-- ]
[args ...] |
appjail pkg |
chroot jail
[args ...] |
appjail pkg |
jail jail
[-j ] [args ...] |
The appjail pkg utility is a wrapper of the
pkg(8)
command to manipulate packages within a jail.
all
is used to run
pkg(8) in
all existing jails. If -e
is specified,
appjail pkg exits when
pkg(8)
returns a non-zero exit status. If -i
is specified,
the content of the file specified by this parameter is used as input for
each call of
pkg(8)
instead of /dev/null. If you want to specify a
pkg(8)
parameter in args and it starts with a dash, you must
use --
or appjail pkg will
interpret it. target is any of the subcommands
described below.
chroot
is used to run
pkg(8) in
a chroot environment using the jail directory. The jail must be started if
it is a thinjail; Otherwise, if it is a thickjail, it can be successfully
executed both started and stopped.
jail
is used to run
pkg(8) in
a given jail. If the -j
parameter is specified,
pkg(8)
installed inside the jail is used instead of the one on the host.
jail
accepts
thin, thick and
linux+debootstrap
jails, while chroot
accepts only
thin and thick jails.
The appjail pkg
utility exits 0 on
success, and >0 if an error occurs. It may fail for one of the
following reasons:
- EX_USAGE:
The command was used incorrectly.
- EX_DATAERR:
- jail is invalid.
- The given command was used in the wrong jail type.
- EX_CONFIG:
There is something wrong regarding the jail configuration, for example:
appjail pkg cannot get some required information.