We recommend building all software inside zones, so you can set up a clean development environment and not "pollute" your main operating environment.
This guide below assumes you are on a LAN with DHCP. We will create a crossbow VNIC on your primary network interface (assumed to be
e1000g0 here, adapt as necessary), which will operate as if the VNIC was plugged directly into your local LAN.
It is also possible to set up static network addressing on a VNIC, as well as use "shared networking" where the local zone's interface would be an alias of one available to the global zone (a guide mentioning this is available here: HOW-TO Setup referential build zone for OpenIndiana Addon Consolidations).
The Distribution Constructor (the software that produces the final ISO Image) does not work inside a local zone.
Here, we are disabling
sync to speed up builds. Note that setting
sync=disabled may result in data loss in a power loss/system crash scenario, so only enable it for your build environment if you don't mind losing data (from recent writes just before the crash):
If your primary interface is not
e1000g0, please substitute for the one that is in use. You can normally find this via "
dladm show-phys" or "
If needed, you can also specify binding of the VNIC to a particular VLAN of your external network with
This step will install the zone by downloading packages from the internet:
This step answers questions you would otherwise have to answer manually via a console-based wizard.
Mount the zone's ZFS dataset so we can access it by running:
Now create the
Remark: the encrypted root password shown here is:
Note also that in the example above, your zone will try to receive networking settings via DHCP. It is possible to set static IP addressing for an "
ip-type=exclusive" local zone by using traditional Solaris methods with files (relative to zone root):
/etc/netmasks and so on; in this case you might want to disable
dhcp-client in the zone. You may also want to make sure that in the zone's
/etc/hosts file the static IP address would be associated with the zone's network name (short hostname and full FQDN), and that name should be used in
/etc/hostname.vnic0 instead of an IP address directly.
You can also configure individual
ipfilter firewall in the "
ip-type=exclusive" zone (GZ's firewall doesn't apply to non-shared LZ networking).
You will now want to attach to the zone's console and watch it boot, and answer any questions if prompted:
You can detach from the console by issuing "
~." without quotes (or "
~~." over chained Unix
Once the zone has booted, you can copy the DNS resolution settings from GZ into the local zone (if networking is the same):
You can now
zlogin into the local zone with:
Try pinging some hosts on the internet. Remember to update the root password.