Self-host Sonatype Nexus Repository with Levelrail

A universal artifact repository for Maven, npm, Docker, PyPI, and more, with proxying and caching.

  • Memory3 GiB
  • Archarm64
  • Services1

How to self-host Sonatype Nexus Repository

  1. Pull the images

    One image is pulled on your server.

    Show images
    • sonatype/nexus3:3.96.3
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 8081.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Sonatype Nexus Repository requirements

Memory
About 3 GiB
Architectures
amd64 image published, arm64 image published
Ports
8081
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
not yet recorded
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 8081 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Sonatype Nexus Repository. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Sonatype Nexus Repository docs page.

Deploy Sonatype Nexus Repository your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Sonatype Nexus Repository from the CLI

levelrail-cli templates deploy nexus --name my-nexus

Deploy Sonatype Nexus Repository with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/nexus/deploy

Sonatype Nexus Repository configuration

Sonatype Nexus Repository services

ServiceImagePortsVolumes
nexus sonatype/nexus3:3.96.3 8081 nexus_data -> /nexus-data

Sonatype Nexus Repository environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
8081
Volumes
1 named mount: nexus_data -> /nexus-data

Sonatype Nexus Repository FAQ

How much memory does Sonatype Nexus Repository need?

The catalog lists about 3 GiB of memory for Sonatype Nexus Repository.

Does Sonatype Nexus Repository run on arm64?

For Sonatype Nexus Repository, an arm64 image is published; amd64 is image published.

Does Sonatype Nexus Repository need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Sonatype Nexus Repository use?

Sonatype Nexus Repository listens on port 8081 inside the stack.

Where does Sonatype Nexus Repository keep its data?

In a named volume: nexus_data mounted at /nexus-data.

Can I deploy Sonatype Nexus Repository on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Sonatype Nexus Repository, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image sonatype/nexus3:3.96.3 is what you deploy there.

levelrail-cli templates deploy nexus --name my-nexus