jswank/nexus3 repository overview

⁠jswank/nexus3

A Dockerfile for Sonatype Nexus 3 Milestone releases, based on Centos.

To run, binding the exposed port 8081 to the host.

$ docker run -d -p 8081:8081 --name nexus jswank/nexus3

To test:

$ curl -u admin:admin123 http://localhost:8081/internal/ping

The karaf console is accessible if running in the foreground and attaching a tty:

$ docker run -t -i -p 8081:8081 --name nexus jswank/nexus3

To (re)build the image:

Copy the Dockerfile and do the build-

$ docker build --rm=true --tag=jswank/nexus3 .

⁠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.

• Three environment variables can be used to control the JVM arguments

  • JAVA_MAX_HEAP, passed as -Xmx. Defaults to 768m.
  • JAVA_MIN_HEAP, passed as -Xms. Defaults to 256m.
  • EXTRA_JAVA_OPTS. Additional options can be passed to the JVM via this variable.

  These can be used supplied at runtime to control the JVM:

  $ docker run -d -p 8081:8081 --name nexus -e JAVA_MAX_HEAP=768m jswank/nexus3
  

  Copy

⁠Persistent 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 container. Since data volumes are persistent until no containers use them, a container can created specifically for this purpose. This is the recommended approach.

$ docker run -d --name nexus-data jswank/nexus3 echo "data-only container for Nexus"
$ docker run -d -p 8081:8081 --name nexus --volumes-from nexus-data jswank/nexus3

1. 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 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 jswank/nexus3