Entando 4.3.1
Features
Download this image
Description
Entando Release 4.3.1
Deprecated
This installation is for a legacy version of the Entando platform on JBoss EAP. For updated instructions and newer versions of the platform focused on Kubernetes visit https://dev.entando.org
Image specifications
The following information was extracted from the dockerfile and other sources.
| Canonical image ID | Entando 4.3.1 |
| Summary | Web Application Example based on the Entando 4.3.1 release |
| Description | Sample of an Entando web application based on engine, admin-console, portal-ui core components. |
| Provider | Entando |
| Maintainer | Pietrangelo Masala <p.masala@entando.com> |
| Source location | https://pmasala@bitbucket.org/pmasala/rh-container.git |
| Repository name | Entando 4.3.1 |
| Image version | 4.3.1 |
| Architecture | amd64 |
| Usage | This image is very generic and does not serve a single use case. Use it as a base to build your own images. |
| Exposed ports | "8080/tcp" |
| User | 1001 |
| Working directory | JAVA_/opt/jdk1.8.0_144 |
Registry tokens
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.
Using Podman login
Run the following command, then enter your registry token credentials when prompted by the terminal.
Pull the image
Image identifiers
Red Hat login
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
Using Podman login
Run the following command, then enter your login credentials when prompted by the terminal.
Pull the image
