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.
Red Hat Enterprise Linux Docker image for Sonatype Nexus Repository Manager.
To run, binding the exposed port 8081 to the host.
$ docker run -d -p 8081:8081 --name nexus sonatype/nexus3
To test:
$ curl -u admin:admin123 http://localhost:8081/service/metrics/ping
admin
/ admin123
$ docker logs -f nexus
/opt/sonatype/nexus
./nexus-data
, is used for configuration,$ docker run -d -p 8081:8081 --name nexus -e INSTALL4J_ADD_VM_PARAMS="-Xms2g -Xmx2g -XX:MaxDirectMemorySize=3g -Djava.util.prefs.userRoot=/some-other-dir" sonatype/nexus3
-Djava.util.prefs.userRoot=/some-other-dir
can be set to a persistent path, which will maintainINSTALL4J_ADD_VM_PARAMS
, passed to the Install4J startup script. Defaults to -Xms1200m -Xmx1200m -XX:MaxDirectMemorySize=2g -Djava.util.prefs.userRoot=${NEXUS_DATA}/javaprefs
.$ docker run -d -p 8081:8081 --name nexus -e NEXUS_CONTEXT=nexus sonatype/nexus3
NEXUS_CONTEXT
, defaults to /
There are two general approaches to handling persistent storage requirements
with Docker. See Managing Data in Containers
for additional information.
$ docker volume create --name nexus-data
$ docker run -d -p 8081:8081 --name nexus -v nexus-data:/nexus-data sonatype/nexus3
$ mkdir /some/dir/nexus-data && chown -R 200 /some/dir/nexus-data
$ docker run -d -p 8081:8081 --name nexus -v /some/dir/nexus-data:/nexus-data sonatype/nexus3
The following information was extracted from the containerfile and other sources.
Summary | The Nexus Repository Manager server with universal support for popular component formats. |
Description | The Nexus Repository Manager server with universal support for popular component formats. |
Provider | Sonatype |
Maintainer | Sonatype <support@sonatype.com> |
The following information was extracted from the containerfile and other sources.
Repository name | Nexus Repository Manager |
Image version | 3.84.0-03 |
Architecture | amd64 |
Exposed ports | 8081:8081 |
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.
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.
Use the following command(s) from a system with podman installed
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.
For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running