container.5 (2011 09)

CONTAINER(5) CONTAINER(5)

Lifecycle

Containers can be created, modiﬁed, deleted, and migrated or cloned across systems via the srp(1M) com-

mand. Containers can be started and stopped in a similar manner to starting and stopping an individual

system, including startup and shutdown processing. When a container is started, you may log into the

container via srp_su(1M), or over a network based shell service such as ssh(1).

Container States

A container can be in one of the following ﬁve states:

Stopped

The container is not available. Its network interface is down, and container ﬁlesystems are not

mounted. Accessing the container using srp_su(1M) in stopped state is not allowed.

Starting

The container is starting and is not accessible by users. srp(1M) will initiate default run level process-

ing (see srp_init(1M)) immediately before transitioning to the started container state. Run level pro-

cessing will complete after the container enters the started state.

Started

The container is up and running, and it is accessible by users. The network interface is up, container

ﬁlesystems are mounted, and container service daemons started.

Stopping

The container is stopping and is not accessible by users. srp(1M) will attempt to shutdown all con-

tainer processes by initiating run-level 0 processing (see srp_init(1M)). If the normal shutdown pro-

cess fails to terminate all container processes, srp will terminate the remaining processes before tran-

sitioning to the container stopped state.

Maintenance

Does not apply to workload containers.

SD is performing software management (install or remove

software) in a container. Container service daemons are stopped and users are not allowed to access

the container in this state.

Namespaces

When HP-UX Containers is enabled on the system, containers may be conﬁgured to use either private or

global name spaces. The contents of a private namespace are only visible to the container. The global

namespace is visible to the Global View, and all containers sharing the global namespace. The following

namespaces maybe conﬁgured to be private or shared, depending on the container type:

- File system (via chroot(2))

-Hostname

- Nodename

- Domainname

- System V IPC

- Loopback IP address ports (127.0.0.*)