HP-UX Containers (SRP) A.03.00 Administrator's Guide

For swinstall, you can reissue the command without targeting the container since the operation

will proceed to the system container even if the product is installed in the global view. For swremove,

you must target the system container that had the issue, since swremove will not proceed past a

global system in which the remove has already occurred.

In some cases, it can be easier to remove the software from the global view and all system containers

and then install it again in the global view and all system containers.

15.5.6 Advanced installation: varying software versions

For a system container with the private filesystem subtype, the version of software with a kernel

component must match the global view. Versions of other software that contain only user-space

commands, libraries, and GUI can be different from the global view.

During SD operation, you can use the local_srp_list option to skip the global view and target

one or more containers.

The following example shows the swinstall command syntax to install different versions of

MY_PRODUCT in two different containers:

# srp -status

NAME TYPE STATE SUBTYPE ROOTPATH

container_B system started private /var/hpsrp/container_B

container_C system started private /var/hpsrp/container_C

# swinstall -x local_srp_list="container_B" –s \

/tmp/myproduct_version_1.depot MY_PRODUCT

# swinstall -x local_srp_list="container_C" –s \

/tmp/myproduct_version_2.depot MY_PRODUCT

15.5.7 Installation methods other than SD

For products that are managed through installation methods other than HP-UX Software Distributor,

such as the tar command, you can install these products inside each individual system container. If

the product installs files under the /usr or /sbin directories, HP recommends that you use a system

container with a private file system.

15.6 Deploying applications

While deploying application in a container, be aware of the read-only restrictions for certain

directories (/usr, /sbin, and /stand) based on the container's file system subtype.

Follow these best practices when deploying applications with system containers:

• Install non-SD applications from inside the container.

This allows the software installation and setup processing to utilize container local namespace

values, such as host name, and file path.

• If you have applied IPFilter for the container, ensure that any additional

ports used by the application are allowed.

When the ipfilter service is enabled for the container, by default the inbound network

connections to the container are blocked. You must configure the ipfilter service to allow

inbound connections to any network ports that the application will listen on.

• Use the custom template to apply additional IPFilter capabilities to the

container for the application.

This will allow you to manage system configuration changes for the container on a per