Software components

Software components install, and possibly configure software on the virtual system pattern.

You can drag a software component onto a virtual image that is on the canvas. If you drag a software component directly onto the canvas, it is automatically added to a virtual image that meets the requirements for that software component.
Tip: If you move a software component from one virtual image to another virtual image, the configuration settings are preserved except for the hosted link on the previous virtual image.

If multiple versions of the software component are available, select the version that you want to deploy with the pattern after you add the software component to the canvas.

If the Docker Pattern Type is installed and enabled on the system, a Docker container software component is available. This software component provides support for using a Docker image to create a Docker container in the instance after it is deployed. If there is more than one Docker container in a pattern, you can link two containers. To link two containers, hover over one of the containers until the blue circle turns orange. Select the circle, drag a connection to the second container until the container is highlighted, and then release. The Docker container software component has these attributes:
Image
Required. Select a Docker image from the Docker registry or upload an image file (in .tar or .tar.gz format). If you select a Docker image from a Docker registry, any attribute values that were specified for the image in the registry are automatically populated.

For more information about working with a Docker registry in PureApplication® Software, see the Related tasks.

Command
Optional. Specify a command to pass to the Docker client after it is started.
Environment variables
Optional. Set the runtime context in the Docker container.
Volumes
Optional. In the container directory field, specify a volume in theDocker container that is mapped to the volume on the host that is specified in the host directory field.
Port Bindings
Optional. Map a port on Docker container to a port on the host.
Advanced options
Restart Policy
Required. Specify whether you want the Docker container to restart automatically if it stops running. Options are:
no
Never restart automatically.
on-failure
Restart if the Docker container stops due to an error. If you select this option, the Docker container restarts five times at the most.
always
Restart the Docker container if it stops, regardless of the cause of the stoppage.
Log Volumes
Optional. Specify the path to a log volume for the middleware in the Docker container to display the logs in the system's Log Viewer page.
Memory Limit
Optional. Specify the maximum amount of memory that the Docker container can use on the host node. By default, the Docker container can use all available memory on the host node. Set this value if you have more than one Docker container in the pattern so that one of the Docker containers cannot use all of the available memory on the host node. If you specify a value here, be sure that it is not smaller than the minimum amount of memory that is needed for the Docker container to run.
CPU Shares (relative weight)
Optional. Specify the number of processor shares that the Docker container can use on the host node. By default, the Docker container can use all available processor shares on the host node. If you specify a value here, be sure that it is not smaller than the minimum number of processor shares that are needed for the Docker container to run.
Privileged
Optional. Run the Docker container with elevated Operating System privileges on the host.
Restriction: Adding components to a virtual image with a Docker container is not supported. For example, adding a DB2 server to a virtual image that contains a Docker container is not supported. You can add more than one Docker container to a single virtual image so that they can share a Docker host.
For more information about working with Docker containers, see the Related concepts.