A Dockerfile for Sonatype Nexus Repository Manager 3, based on CentOS.
To run, binding the exposed port 8081 to the host.
$ docker run -d -p 8081:8081 --name nexus sonatype/docker-nexus3
To test:
$ curl -u admin:admin123 http://localhost:8081/service/metrics/ping
To (re)build the image:
Copy the Dockerfile and do the build-
$ docker build --rm=true --tag=sonatype/docker-nexus3 .
-
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_MEM
, passed as -Xmx. Defaults to1200m
. -
JAVA_MIN_MEM
, passed as -Xms. Defaults to1200m
. -
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_MEM=768m sonatype/docker-nexus3
-
-
Another environment variable can be used to control the Nexus Context Path
NEXUS_CONTEXT
, defaults to /
This can be supplied at runtime:
$ docker run -d -p 8081:8081 --name nexus -e NEXUS_CONTEXT=nexus sonatype/docker-nexus3
There are two general approaches to handling persistent storage requirements with Docker. See Managing Data in Containers for additional information.
- 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/docker-nexus3
- 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/docker-nexus3
Looking to contribute to our Docker image but need some help? There's a few ways to get information or our attention:
- File a public issue here on GitHub
- Check out the Nexus3 tag on Stack Overflow
- Check out the Nexus Repository User List