Configure Nexus for Artifact Caching and Docker Registry

Your CI pipeline spends 15 minutes downloading Maven dependencies from external repositories. Docker Hub throttles you with rate limits, and the npm registry is slow under load. Nexus Repository Manager solves all three problems in one tool. It caches artifacts after the first request, provides a private Docker Registry, and acts as a single endpoint for all package managers. Estimated traffic savings: up to $200 per month for a mid-sized team, build acceleration up to 90x.

Contact us for an audit — we'll evaluate your infrastructure. Our engineers have 10+ years of experience in administering Nexus on Kubernetes clusters and bare-metal, with 40+ successful projects.

How Nexus Accelerates Builds

Nexus caches dependencies after the first download. On subsequent builds, artifacts are served from local storage. Latency drops from 15 minutes to under 10 seconds. This is especially noticeable during frequent container restarts in CI.

Repository Types and When to Use Them

Nexus works with three repository types:

A typical Maven configuration:

maven-public (group)
├── maven-releases (hosted)
├── maven-snapshots (hosted)
└── maven-central (proxy → https://repo1.maven.org/maven2/)

In ~/.m2/settings.xml, developers only need to specify http://nexus.company.com/repository/maven-public/.

Why Choose Nexus Over Artifactory?

Nexus Open Source is free and requires no licensing. It's simpler to set up: a basic scenario takes half the time compared to Artifactory. Yet it provides enough functionality for most mid-sized companies. It supports Maven, npm, Docker, PyPI, and others.

License comparison: Artifactory Pro starts at $12,000 per year for 5 users, Nexus OSS is $0. Performance difference is negligible given the same resources.

Installation and Minimal Configuration

Nexus OSS is distributed as a tar.gz and a Docker image. For production, we recommend Docker with an external data volume:

version: "3"
services:
  nexus:
    image: sonatype/nexus3:3.68.0
    volumes:
      - nexus-data:/nexus-data
    ports:
      - "8081:8081"
      - "8082:8082" # Docker registry port
    environment:
      - INSTALL4J_ADD_VM_PARAMS=-Xms2703m -Xmx2703m -XX:MaxDirectMemorySize=2703m
    restart: unless-stopped
volumes:
  nexus-data:

JVM parameters are critical. Sonatype documentation recommends allocating at least 2/3 of available RAM to Nexus — on a host with 8 GB, set -Xmx4g. Insufficient memory leads to OutOfMemoryError: Direct buffer memory during intensive Docker registry operations.

The initial admin password after first launch is in /nexus-data/admin.password.

Configuring Docker Registry

Nexus can act as a Docker registry — hosted for private images and proxy for Docker Hub (bypassing rate limits):

docker-hub (proxy → https://registry-1.docker.io) → port 8083
docker-internal (hosted) → port 8082
docker-all (group) → port 8084

Each Docker repository requires a separate HTTP port — a limitation of the Docker Registry v2 protocol. In Nginx, add a location for each port or use subdomains.

CI authentication:

docker login nexus.company.com:8082 -u ci-user -p $NEXUS_PASSWORD docker push nexus.company.com:8082/myapp:1.0.0 

Security and Roles

By default, Nexus creates roles nx-admin, nx-anonymous, nx-deploy. For production, we recommend:

• Disable anonymous access (Administration → Security → Anonymous Access).
• Create separate roles for CI (nx-deploy-role with permissions on specific repositories) and developers (read-only on proxy repositories).
• Configure LDAP integration for corporate authentication.

Permissions are assigned at the repository level via Repository Content Selectors — you can restrict a CI user to specific package groups.

Nexus OSS vs Pro Comparison

For most companies, the OSS version is sufficient. Pro is justified when strict compliance requirements or SAML integration is needed.

Artifact Cleanup and Cleanup Policies

Without cleanup policies, Nexus grows indefinitely. Create a Cleanup Policy for:

• maven-snapshots-cleanup: delete SNAPSHOT artifacts older than 30 days that haven't been accessed in the last 7 days.
• docker-cleanup: delete untagged Docker images older than 7 days.

Policies are applied to repositories in Administration → Repository → Cleanup Policies. The Cleanup service runs on a schedule (default: once per day).

After cleanup, always run Compact Blob Store — otherwise, disk space is not freed; data is just marked as deleted.

Setup Plan

1. Choose Nexus version (OSS or Pro).
2. Deploy the container via Docker.
3. Configure transport: HTTP ports, TLS.
4. Create a proxy repository for the target package registry.
5. Create hosted and group repositories.
6. Configure users and roles.
7. Apply Cleanup Policies.

What's Included in Turnkey Setup

• Installation and basic configuration (Docker, volume, JVM).
• Proxy repositories for Maven, npm, Docker, PyPI.
• Hosted repositories for your artifacts.
• Group repository for a single endpoint.
• Docker Registry (hosted, proxy, group) with separate ports.
• LDAP integration for corporate authentication.
• Role and security policy creation.
• Cleanup policies and automatic cleanup.
• Documentation and team training (1–2 hours).

We guarantee stable operation and post-implementation support. Order Nexus setup — get an engineer consultation.

<settings>
  <mirrors>
    <mirror>
      <id>nexus-maven-public</id>
      <mirrorOf>*</mirrorOf>
      <url>http://nexus.company.com/repository/maven-public/</url>
    </mirror>
  </mirrors>
</settings>

Timelines

Full production setup — 1–3 days. Pricing is determined after an infrastructure audit.