Red Hat Directory Server Container

13.1-1764432956

latest

13.1

Overview

Description

Red Hat Directory Server is an enterprise-class LDAP directory server. This container image provides the 389 Directory Server for RHEL 10, offering scalable, secure directory services for authentication, authorization, and identity management. The image is maintained by Red Hat and updated regularly as part of the Red Hat Directory Server product line.

Configuration

Environment variables for customization:

DS_DM_PASSWORD - set password for cn=Directory Manager, default is randomly generated
DS_ERRORLOG_LEVEL - set the log level for ns-slapd, default is 266354688
DS_MEMORY_PERCENTAGE - set LDBM autotune percentage (nsslapd-cache-autosize), default is 25
DS_REINDEX - run database reindex task (db2index) on startup
DS_STARTUP_TIMEOUT/DS_STOP_TIMEOUT - set container timeouts in seconds, default is 60 seconds
DS_SUFFIX_NAME - use suffix as a basedn in the dsrc file, default one is derived from the hostname. NOTE: this doesn't create the suffix and/or backend.

Technology Preview Notice

This feature is provided as a Technology Preview and is not fully supported under Red Hat subscription level agreements. Technology Preview features are provided to allow customers to gain early access to new features and provide feedback. For more information about Technology Preview support, see https://access.redhat.com/support/offerings/techpreview/

Products using this container

Red Hat Directory Server

Red Hat Directory Server is an LDAPv3 compliant server

Containerized application

Security

Technical information

General information

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

Summary	Red Hat Directory Server
Description	Red Hat Directory Server Container
Provider	Red Hat
Maintainer	Red Hat, Inc.

Technical information

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

Repository name	redhat-ds
Image version	v13.1
Architecture	amd64
Exposed ports	3389:3636

Packages

Containerfile

Get this image

Terms & conditionsBefore downloading or using this Container, you must agree to the Red Hat subscription agreement located at redhat.com/licenses. If you do not agree with these terms, do not download or use the Container. If you have an existing Red Hat Enterprise Agreement (or other negotiated agreement with Red Hat) with terms that govern subscription services associated with Containers, then your existing agreement will control.

Using registry tokens

Registry

Repository

Image Digest

Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.

Using OpenShift secrets

First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.

Then, use the following from the command line or from the OpenShift Dashboard GUI interface.

Using podman login

Use the following command(s) from a system with podman installed

Using docker login

Use the following command(s) from a system with docker service installed and running

Registry

Repository

Image Digest

Use the following instructions to get images from a Red Hat container registry using your Red Hat login.

Using OpenShift

For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.

Using podman login

Use the following command(s) from a system with podman installed

Using docker login

Use the following command(s) from a system with docker service installed and running

Get the source

Registry

Repository

Image Digest

Getting source containers

Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.

Although they are packaged as containers, source containers cannot be run. So instead of using podman pull to get them to your system, use the skopeo command.
Source containers are named based on the binary containers they represent. So, for example, to get the source container for a particular standard RHEL UBI 8 container (registry.access.redhat.com/ubi8/ubi8.1-397) you simply append -source to get the source code container for that image (registry.access.redhat.com/ubi8/ubi8.1-397-source).
The skopeo command is recommended for getting source containers. With skopeo, you copy a source container to a directory on your local system for you to examine.
Once a source container is copied to a local directory, you can use a combination of tar,gzip, and rpm commands to work with that content.

Step one

Use skopeo to copy the source image to a local directory

Step two

Inspect the image

Step three

Untar the contents

Step four

Begin examining and using the content.

Description

Configuration

Environment variables for customization:

DS_DM_PASSWORD - set password for cn=Directory Manager, default is randomly generated

DS_ERRORLOG_LEVEL - set the log level for ns-slapd, default is 266354688

DS_MEMORY_PERCENTAGE - set LDBM autotune percentage (nsslapd-cache-autosize), default is 25

DS_REINDEX - run database reindex task (db2index) on startup

DS_STARTUP_TIMEOUT/DS_STOP_TIMEOUT - set container timeouts in seconds, default is 60 seconds

DS_SUFFIX_NAME - use suffix as a basedn in the dsrc file, default one is derived from the hostname. NOTE: this doesn't create the suffix and/or backend.

Technology Preview Notice

Getting source containers

Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.

Although they are packaged as containers, source containers cannot be run. So instead of using podman pull to get them to your system, use the skopeo command.

Source containers are named based on the binary containers they represent. So, for example, to get the source container for a particular standard RHEL UBI 8 container (registry.access.redhat.com/ubi8/ubi8.1-397) you simply append -source to get the source code container for that image (registry.access.redhat.com/ubi8/ubi8.1-397-source).

The skopeo command is recommended for getting source containers. With skopeo, you copy a source container to a directory on your local system for you to examine.

Once a source container is copied to a local directory, you can use a combination of tar,gzip, and rpm commands to work with that content.

Description

Configuration

Technology Preview Notice

Products using this container

Red Hat Directory Server

Published

Release category

Digest

General information

Technical information

Using OpenShift secrets

Using podman login

Using docker login

Using OpenShift

Using podman login

Using docker login

Getting source containers

Step one

Step two

Step three

Step four

Platforms

Products & services

Try, buy, sell

Help

About Red Hat Ecosystem Catalog

Red Hat legal and privacy links

Red Hat legal and privacy links

Red Hat Directory Server Container

Description

Configuration

Technology Preview Notice

Products using this container

Red Hat Directory Server

Published

Release category

Digest

General information

Technical information

Using OpenShift secrets

Using podman login

Using docker login

Using OpenShift

Using podman login

Using docker login

Getting source containers

Step one

Step two

Step three

Step four