forked from sonatype/docker-nexus3
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
revert erroneous commit(wrong branch)
- Loading branch information
1 parent
e651dd9
commit eef5f06
Showing
1 changed file
with
78 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,82 @@ | ||
# sonatype/nexus3 | ||
|
||
|
||
A Dockerfile for Sonatype Nexus Repository Manager 3, based on CentOS. | ||
|
||
# DEPRECATED | ||
This repository content has moved to https://github.com/sonatype/docker-nexus3 in order to properly enable auto-builds on Dockerhub. | ||
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:https://localhost:8081/service/metrics/ping | ||
``` | ||
|
||
To (re)build the image: | ||
|
||
Copy the Dockerfile and do the build- | ||
|
||
``` | ||
$ docker build --rm=true --tag=sonatype/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_MEM`, passed as -Xmx. Defaults to `1200m`. | ||
|
||
* `JAVA_MIN_MEM`, passed as -Xms. Defaults to `1200m`. | ||
|
||
* `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 sonatype/nexus3 | ||
``` | ||
|
||
|
||
### Persistent Data | ||
|
||
There are two general approaches to handling persistent storage requirements | ||
with Docker. See [Managing Data in Containers](https://docs.docker.com/userguide/dockervolumes/) | ||
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 sonatype/nexus3 echo "data-only container for Nexus" | ||
$ docker run -d -p 8081:8081 --name nexus --volumes-from 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 | ||
``` |