BRANDS(7) Standards, Environments, and Macros BRANDS(7)


brands - alternate operating environments for non-global zones


The branded zone (BrandZ) framework extends the Solaris Zones
infrastructure described in zones(7) to include the creation of brands,
which provide non-global zones that contain non-native operating

The term "brand" can refer to a wide range of operating environments. All
brand management is performed as extensions to the current zones

Every zone is configured with an associated brand. The brand type is used
to determine which scripts are executed when a zone is installed and
booted. In addition, a zone's brand is used to properly identify the
correct application type at application launch time. The default brand
is determined by the installed distribution in the global zone.

A branded zone will support exactly one brand of non-native binary, which
means that a branded zone provides a single operating environment. Once a
zone has been assigned a brand, that brand cannot be changed or removed.

BrandZ extends the zones tools in the following ways:

o A brand is an attribute of a zone, set at zone create time.

o The zonecfg tool (see zonecfg(8)) is used to set a zone's
brand type and configure the zone.

o The zoneadm tool (see zoneadm(8)) is used to report a zone's
brand type and administer the zone.

Device Support

The devices supported by each zone are documented in the man pages and
other documentation for that brand. The zones infrastructure detects any
attempt to add an unsupported device and issues a warning to the
administrator. If the administrator chooses to add an unsupported device
despite that warning, that device might or might not work as expected.
The configuration will be untested and unsupported.


See attributes(7) for a description of the following attributes:

|Interface Stability | Evolving |


attributes(7), zones(7), zoneadm(8), zonecfg(8)

illumos May 23, 2021 BRANDS(7)