Description

Sonatype Nexus Repository Manager

Red Hat Enterprise Linux Docker image for Sonatype Nexus Repository Manager.

Running

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

Notes

• Default credentials are: admin / admin123
• It can take some time (2-3 minutes) for the service to launch in a
  new container. You can tail the log to determine once Nexus is ready:

$ docker logs -f nexus

• Installation of Nexus is to /opt/sonatype/nexus.
• A persistent directory, /nexus-data, is used for configuration,
  logs, and storage. This directory needs to be writable by the Nexus
  process, which runs as UID 200.
• There is an environment variable that can used to pass JVM arguments to the startup script
  This can be supplied at runtime:
  $ 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
  Of particular note, -Djava.util.prefs.userRoot=/some-other-dir can be set to a persistent path, which will maintain
  the installed Nexus Repository License if the container is restarted.
  • INSTALL4J_ADD_VM_PARAMS, passed to the Install4J startup script. Defaults to -Xms1200m -Xmx1200m -XX:MaxDirectMemorySize=2g -Djava.util.prefs.userRoot=${NEXUS_DATA}/javaprefs.
• Another environment variable can be used to control the Nexus Context Path
  This can be supplied at runtime:
  $ docker run -d -p 8081:8081 --name nexus -e NEXUS_CONTEXT=nexus sonatype/nexus3
  • NEXUS_CONTEXT, defaults to /

Persistant Data

There are two general approaches to handling persistent storage requirements
with Docker. See Managing Data in Containers
for additional information.

1. Use a data volume. Since data volumes are persistent
   until no containers use them, a volume can be created specifically for
   this purpose. This is the recommended approach.
   $ docker volume create --name nexus-data
$ docker run -d -p 8081:8081 --name nexus -v nexus-data:/nexus-data sonatype/nexus3
2. Mount a host directory as the volume. This is not portable, as it
   relies on the directory existing with correct permissions on the host.
   However it can be useful in certain situations where this volume needs
   to be assigned to certain specific underlying storage.
   $ 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