Red Hat Enterprise Linux 7 Deprecated
Description
On June 30th, 2024, Red Hat Enterprise Linux 7 will transition from Maintenance Life Cycle 2 phase to Extended Life phase. Software maintenance, new bug fixes and security errata will no longer be provided for the Red Hat Enterprise Linux 7 product family. This includes all RHEL7-based and UBI7-based container images, such as rhel7/rhel, ubi7, ubi7/python-38, etc. The Red Hat Enterprise Linux 7 Extended Lifecycle Support add-on subscription provides Red Hat Enterprise Linux 7 customers with access to limited software updates, and, if desired, these updates should be applied to all rhel7-based and ubi7-based container images in use. For a more complete list of affected container images please see the container component list for Red Hat Enterprise Linux 7 [1] and Red Hat Universal Base Image 7 on the Red Hat Ecosystem Catalog [2].
Please see the following FAQ for more information about the Extended Life Phase and the Extended Lifecycle Support add-on subscription [3].
[1] https://catalog.redhat.com/software/container-stacks/detail/5eed1bf53eda773b377f4909
[2] https://catalog.redhat.com/software/container-stacks/detail/5eed413846bc301a95a1e9a1
[3] https://access.redhat.com/articles/7005471
The Red Hat Enterprise Linux Base image is designed to be a fully supported foundation for your containerized applications. This base image provides your operations and application teams with the packages, language runtimes and tools necessary to run, maintain, and troubleshoot all of your applications. This image is maintained by Red Hat and updated regularly. It is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. When used as the source for all of your containers, only one copy will ever be downloaded and cached in your production environment. Use this image just like you would a regular Red Hat Enterprise Linux distribution. Tools like yum, gzip, and bash are provided by default. For further information on how this image was built look at the /root/anacanda-ks.cfg file.
Documentation
Products using this container
General information
The following information was extracted from the containerfile and other sources.
| Summary | Provides the latest release of Red Hat Enterprise Linux 7 in a fully featured and supported base image. |
| Description | The Red Hat Enterprise Linux Base image is designed to be a fully supported foundation for your containerized applications. This base image provides your operations and application teams with the packages, language runtimes and tools necessary to run, maintain, and troubleshoot all of your applications. This image is maintained by Red Hat and updated regularly. It is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. When used as the source for all of your containers, only one copy will ever be downloaded and cached in your production environment. Use this image just like you would a regular Red Hat Enterprise Linux distribution. Tools like yum, gzip, and bash are provided by default. For further information on how this image was built look at the /root/anacanda-ks.cfg file. |
| Provider | Red Hat |
Technical information
The following information was extracted from the containerfile and other sources.
| Repository name | rhel7 |
| Image version | 7.9 |
| Architecture | amd64 |
| Exposed ports | [] |
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
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
Use the following instructions to get images from a Red Hat container registry without providing authentication.
Using oc
A container image made to run with OpenShift platforms can either be pulled from the command line or from the OpenShift Dashboard GUI interface.
Using podman
Use the following command(s) from a system with podman installed
Using docker
Use the following command(s) from a system with docker service installed and running
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.
