HP-UX Containers (SRP) A.03.01 Release Notes

11
Workaround:
Use a common user database, such as LDAP or NIS, for the global view and the containers of
each system where containers will be imported.
The srp or srp_sys command may fail and print the error message, ‘“:POSIX”
is not exported by the Errno module’, followed by a series of perl
diagnostics. If the PERL5LIB environment variable is set to an alternate path, the
referenced perl version may be incompatible with the HP-UX Containers product. The HP-UX
Containers product has been validated with the Perl version E.5.8.8.F, shipped with the
HP-UX 11i OE.
Workaround:
Unset the PERL5LIB environment variable before running the srp or srp_sys commands.
Alternately, set the PERL5LIB environment variable to /opt/perl/lib/5.8.8.
The srp command does not delete a default route from the system routing
tables when a default route for a started container is changed. The srp
command supports changing a default route for a started container. However, the previous
configuration for the default route is not deleted from the system routing tables.
Workaround:
Delete the default route associated with the old gateway IP address. For example:
# route delete default 192.168.1.1
1.10 Compatibility with other products
The following compatibility issues should be noted before you install the HP-UX Containers product:
HPVM
Installing HP-UX Containers on an HPVM Host is not supported. However, you can install and
configure HP-UX Containers on an HPVM guest.
Trusted Systems
HP-UX Containers is not supported on a system with Trusted Systems enabled.
HP-UX Whitelisting
The HP-UX WhiteListing product cannot be installed on a system with HP-UX Containers
A.03.0 (or later) installed.
ContainmentExt
Enabling HP-UX Containers will set the value of the system tunable cmpt_restrict_tl to 1
to restrict communication between containers using the STREAMS local transport drivers. This
setting will also affect communication between compartments that are not associated with HP-
UX Containers. Refer to cmpt_restrict_tl(5) and compartments(5) for more
information.
1.11 Restrictions on system containers
System containers provide the image of an individual system with its own root file system, system
services, hostname, private user/group management that enable similar or different workloads to
execute independently on the same physical system. Although each system container appears to be a
separate system to the local user, all system containers are executing within a single instance of the