IBM FileNet Content Search Services - 5.5.6

Overview

Features

Release categoryGenerally Available

Exposed ports8199/tcp, 8191/tcp

Privilege modeUnprivileged

User50001

This will require authentication. View other options.

IBM Cloud Pak for Automation V20.0.3 - IBM FileNet Content Search Services - 5.5.6

Security

Specifications

The following information was extracted from the dockerfile and other sources.

Canonical image ID	IBM FileNet Content Search Services - 5.5.6
Summary	IBM® Content Search Services is a search engine that you can use for content-based retrieval functions.
Description	The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
Provider	IBM Corporation
Maintainer	Red Hat, Inc.
Repository name	IBM® Content Search Services
Image version	5.5.6
Architecture	amd64
Exposed ports	"8199/tcp","8191/tcp"
User	50001
Working directory	JAVA_/opt/ibm/java/jre

Packages

Get this image

Manifest List Digest Recommended

Use this digest to pull the image on any supported architecture. It automatically selects the correct image for your system.

Image Digest

Unique identifier for this specific architecture's build. Use only if you need to pin exactly to this specific platform.

This certified image is distributed by a third party registry. Use the information above to pull the image or view pulling certified images from third party registries for more information.

log in to MyIBM Container Software Library with the IBMid and password that are associated with the entitled software.
In the Container software library tile, verify your entitlement on the View library page, and then go to Get entitlement key to retrieve the key.
Create a pull secret by running a kubectl create secret command.
$ kubectl create secret docker-registry admin.registrykey --docker-server=cp.icr.io --docker-username=cp --docker-password="<API_KEY_GENERATED>" --docker-email=<USER_EMAIL>
Note: The cp.icr.io value for the docker-server parameter is the only registry domain name that contains the images.

Note: Use “cp” for the docker-username. The docker-email has to be a valid email address (associated to your IBM ID). Make sure you are copying the Entitlement Key in the docker-password field within double-quotes.