Installing and Administering Solaris Container Manager 3.6.1

Non-Global Zones

A non-global zone does not need a dedicated CPU, a physical device, or a portion of physical memory. These resources can be shared across a number of zones that run within a single domain or system. Zones can be booted and rebooted without affecting other zones on the system. Each zone can provide a customized set of services. To enforce basic process isolation, a process can “see” or signal only those processes that exist in the same zone. Basic communication between zones is enabled by giving each zone at least one logical network interface. An application running in one zone cannot see the network traffic of another zone even though the respective streams of packets travel through the same physical interface.

Each zone that requires network connectivity is configured with one or more dedicated IP addresses.

For more information about zones, see System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.