A series of example Dockerfiles for Sonatype Nexus Repository Manager 3.
3.2.0-alpine
(3.2/alpine/Dockerfile)3.2.0-centos
(3.2/centos/Dockerfile)3.2.0-ubuntu
(3.2/ubuntu/Dockerfile)3.2.1-alpine
,3.2-alpine
(3.2.1/alpine/Dockerfile)3.2.1-centos
,3.2-centos
(3.2.1/centos/Dockerfile)3.2.1-ubuntu
,3.2-ubuntu
(3.2.1/ubuntu/Dockerfile)3.3.0-alpine
,3.3-alpine
(3.3.0/alpine/Dockerfile)3.3.0-centos
,3.3-centos
(3.3.0/centos/Dockerfile)3.3.0-ubuntu
,3.3-ubuntu
(3.3.0/ubuntu/Dockerfile)
Firstly, these images and Dockerfiles are meant as examples and are not supported in any way, shape, or form. If you need a supported Docker image, you should head over to the Sonatype image
Secondly, I'm practicing semver with the tags. If you choose 3.2, you'll get minor updates like 3.2.1 for example. If you need to be stuck to an exact version, use the full version ala 3.2.0 or 3.2.1 :)
To run, binding the exposed port 8081 to the host.
$ docker run -d -p 8081:8081 --name nexus darthhater/nexus3
To test:
$ curl -u admin:admin123 http://localhost:8081/service/metrics/ping
To (re)build the image(s):
Copy the Dockerfile and do the build-
$ docker build --rm=true --tag=darthhater/nexus3 .
-
This repo learns and leans heavily on sonatype/nexus3. Expect updates from that repo to make it here slower.
-
New Dockerfiles can be generated from the templates by running
update.sh
.- Example to update:
./update.sh -n 3.2.1-01 -b 8 -l 112 -s 15 -g 2.23-r3
- n) NEXUS_VERSION
- b) VERSION_MAJOR (Java)
- l) VERSION_MINOR (Java)
- s) VERSION_BUILD (Java)
- g) GLIBC_VERSION (Alpine fun times)
- Example to update:
-
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 darthhater/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 darthhater/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 darthhater/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 darthhater/nexus3
The Dockerfile contains two build arguments (NEXUS_VERSION
& NEXUS_DOWNLOAD_URL
) that can be used to customize what
version of, and from where, Nexus Repository Manager is downloaded. This is useful mostly for testing purposes as the
Dockerfile may be dependent on a very specific version of Nexus Repository Manager.
docker build --rm --tag nexus-custom --build-arg NEXUS_VERSION=3.x.y --build-arg NEXUS_DOWNLOAD_URL=http://.../nexus-3.x.y-unix.tar.gz .
Welp, this was made out of the kindness of my own heart. I'll be clear, this is not supported by Sonatype. SOOOOO, that said, don't go barking to Sonatype for help, you are using these images at your own risk tolerance. DOOOOO file issues here, and get involved, if you find a problem. This is open source and hopefully the community will come to the rescue for those things that are useful.