The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
Container with the openssl binary, giving the ability to work with cryptographic keys and certificates needed for web servers. The openssl container provides an openssl command-line tool for using the various functions of the OpenSSL crypto library. Using the OpenSSL tool, you can generate private keys, create certificate signing requests (CSRs), and display certificate information.
To get the openssl container image on your local system, run the following:
$ podman pull registry.access.redhat.com/ubi8/openssl
To run the openssl command inside the openssl container, run:
$ podman run --rm -v ./mykeys:/keys:z \
registry.access.redhat.com/ubi8/openssl \
<openssl_command>
This command performs the following actions:
-v ./mykeys:/keys:z option mounts the mykeys folder on the host to the keys folder inside the container. The folder needs to be created if it does not exist already.keys folder from the mykeys folder on the host even if you exit the container.z option is needed to set correct SELinux labels.Examples of the <openssl_command> are the following:
Generate a private RSA key:
genpkey -algorithm RSA -out key.pem
Generate a private Elliptic Curve (EC) key:
ecparam -genkey -name prime256v1 -noout -out ec256-key-pair.pem
-name option with secp384r1 or secp521r1 values for 384 or 521-bit key generation, respectively.Display the certificate:
x509 -noout -text -in /etc/rhsm/ca/redhat-uep.pem
Request the certificate:
req -new -key key.pem -out req.pem
mykeys/key.pem and saves it into the mykeys/req.pem file.Verify the certificate:
verify -CAfile root.pem -untrusted intermediate.pem www.example.org.pem
root.pem and intermediate.pem files from the Certificate Authority (CA) with this command. Both files are placed in the keys folder.openssl man page
The following information was extracted from the dockerfile and other sources.
| Canonical image ID | openssl |
| Summary | OpenSSL Portable Certificate and Signing Container |
| Description | Container with the openssl binary, giving ability to work with cryptographic keys and certificates needed for web servers. |
| Provider | Red Hat |
| Maintainer | SoftwareCollections.org <sclorg@redhat.com> |
| Repository name | ubi8/openssl |
| Image version | 8.9 |
| Architecture | amd64 |
| GPG Key ID |
Use a registry service account token to authenticate your container client. This allows you to pull images without using your personal Red Hat credentials, which is recommended for CI/CD pipelines and automated deployments.
Run the following command, then enter your registry token credentials when prompted by the terminal.
Pull the image
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
Run the following command, then enter your login credentials when prompted by the terminal.
Pull the image
Use the following instructions to get images from a Red Hat container registry without providing authentication.
Use the following command(s) from a system with podman installed.
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.
Use skopeo to copy the source image to a local directory
Inspect the image
Untar the contents
Begin examining and using the content.