Known Issues

This is a short list of known issues.

88 character mount path limitation

There is a know mountpoint path length limitation issue on FreeBSD which is set to a historical 88 character limit.

This issue does not affect iocage jails from functioning properly, but can present challenges when diving into ZFS snapshots (cd into .zfs/snapshots, tar, etc.).

ZFS snapshot creation and rollback is not affected.

To workaround this issue iocage 1.6.0 introduced a hack88 property.

Example:

Shut down jail:

iocage stop myjail

Set the hack88 property to “1”:

iocage set hack88=1

Start jail:

iocage start myjail

To revert back to full paths repeat the procedure but set hack88=0.

To create a system wide default (introduced in 1.6.0) for all newly created jails use:

iocage set hack88=1 default

Property validation

iocage does not validate properties right now. Please refer to man page to see what is supported for each property. By default iocage pre-configures each property with a safe default.

VNET/VIMAGE issues

VNET/VIMAGE can cause unexpected system crashes when VNET enabled jails are destroyed - that is when the jail process is killed, removed, stopped.

As a workaround iocage allows a warm restart without destroying the jail. By default the restart sub-command will execute a warm restart.

Example:

iocage restart UUID

FreeBSD 10.1-RELEASE is stable enough to run with VNET and warm restarts. There are production machines with iocage and VNET jails running well beyond 100 days of uptime running both PF and IPFW.

Table Of Contents

Previous topic

Create a Debian Squeeze jail (GNU/kFreeBSD)

Next topic

FAQ

This Page