How to Set Up Harbor Container Registry on Ubuntu VPS with Docker

Introduction to Harbor Architecture

Harbor is an enterprise-class CNCF-graduated container registry that secures artifacts with policies and role-based access control. It consists of multiple components: the Core API, Jobservice, Registry (distribution), Redis, PostgreSQL, Trivy (for vulnerability scanning), and a Portal frontend. It fundamentally relies on Docker Compose or Kubernetes for orchestration.

Modern system administration requires robust, scalable open-source tooling. Deploying Harbor fundamentally shifts control away from expensive SaaS platforms and places it directly into the hands of the infrastructure engineer. This comprehensive tutorial will rigorously guide you through deploying Harbor on an Ubuntu Linux Virtual Private Server, ensuring a production-ready, hardened environment.

Hardware Sizing & Prerequisite Checklist

Before initializing the deployment, your infrastructure must meet strict baseline requirements. Failing to provision adequate hardware will invariably result in critical service degradation or kernel out-of-memory (OOM) panics.

• Compute & Memory: Minimum 4 vCPU cores, 8GB RAM (strict requirement due to Trivy scanner and multiple microservices), 40GB+ NVMe SSD, Ubuntu 22.04 LTS, Docker, and Docker Compose.
• Operating System: A freshly installed Ubuntu Linux VPS (preferably 22.04 LTS or 24.04 LTS).
• Networking: A statically assigned IPv4 address and a registered domain name (e.g., yourdomain.com) with A records pointing to your server’s IP.
• Software Dependencies: `curl`, `wget`, `git`, and `ufw` firewall pre-installed.

Step-by-Step Linux Installation & Configuration

The contemporary standard for application deployment relies heavily on containerization. Utilizing Docker and Docker Compose ensures complete environmental parity and isolates the application layer from the underlying host OS.

Execute the following commands to install the Docker engine directly from the official repository:

sudo apt update && sudo apt upgrade -y
sudo apt install ca-certificates curl gnupg lsb-release -y
sudo mkdir -m 0755 -p /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin -y
sudo systemctl enable docker --now

Download the latest offline installer from GitHub (`wget https://github.com/goharbor/harbor/releases/…`). Extract the tarball. Edit the `harbor.yml` configuration to set your hostname and passwords. Run `./install.sh –with-trivy` to execute the installer, which automatically generates the Docker Compose stack and starts the services.

Production Docker Compose Configuration

# Harbor utilizes an automated installer script rather than a raw docker-compose file.
# You must download the harbor-offline-installer.tgz package.
# Extract it, copy harbor.yml.tmpl to harbor.yml, and configure it:

hostname: registry.yourdomain.com
http:
  port: 80
# Comment out HTTPS if terminating via external Nginx/Traefik
# https:
#   port: 443
#   certificate: /your/certificate/path
#   private_key: /your/private/key/path

harbor_admin_password: StrongAdminPassword123
database:
  password: StrongDatabasePassword123

data_volume: /var/log/harbor

Nginx Reverse Proxy & TLS Configuration

Directly exposing application ports to the public internet violates zero-trust architectural principles. An Nginx reverse proxy handles load balancing, HTTP header manipulation, and essential TLS termination.

sudo apt install nginx -y

Create the following configuration block at `/etc/nginx/sites-available/harbor`:

server {
    listen 80;
    server_name registry.yourdomain.com;
    
    # Required for large image uploads
    client_max_body_size 0;
    
    location / {
        proxy_pass http://127.0.0.1:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Performance Tuning & Benchmark Comparison Table

Docker image layers can quickly consume local disk space. Configure Harbor’s built-in Garbage Collection via the UI to run on a weekly schedule. For storage backends, map the `data_volume` to an S3 bucket or NFS share for infinite scalability.

To demonstrate the efficacy of this deployment, we compare the self-hosted metrics against standard industry baselines:

| Component | Resource Usage | Optimization |
|---|---|---|
| Trivy Scanner | 2-4GB RAM (Bursts) | Run scans off-peak |
| Jobservice | 500MB RAM | Increase concurrency in harbor.yml |
| PostgreSQL | 1GB RAM | Tune shared_buffers |

Security Hardening: UFW, SSL, and Permissions

Enable Trivy vulnerability scanning on every image push. Configure deployment webhooks to prevent pulling images with Critical vulnerabilities. Enforce OIDC (SSO) login for all internal developers instead of local accounts.

Deploy the Uncomplicated Firewall (UFW) to enforce a strict default-deny policy, explicitly allowing only essential traffic protocols:

sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow 22/tcp
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable

Secure the endpoint with Let’s Encrypt TLS certificates:

sudo apt install certbot python3-certbot-nginx -y
sudo certbot --nginx -d yourdomain.com --agree-tos --redirect -m [email protected]

Real-World Troubleshooting FAQ

Why do large image pushes fail with ‘413 Request Entity Too Large’?

This is entirely due to Nginx’s default client body size limit. You must set `client_max_body_size 0;` (unlimited) in your Nginx configuration, as Docker pushes large blobs during the upload phase.

How do I upgrade Harbor to a new version?

Stop Harbor (`docker compose down`). Backup the database. Download the new installer, migrate your `harbor.yml` using the provided migration tool, and run `./install.sh` again.

Does Harbor support Helm charts?

Yes, Harbor functions as an OCI-compliant registry, meaning it can store and serve Docker images, Helm charts, and even WebAssembly modules natively.

---

Advanced Kernel & Network Optimization (Deep Dive)

Beyond the fundamental installation, extracting maximum performance from your Linux VPS requires delving into kernel-level TCP/IP stack tuning and file descriptor management. Applications that handle substantial concurrent connections, webhooks, or asynchronous database transactions inevitably encounter bottlenecks at the operating system layer if left at default configurations.

The Linux kernel’s default parameters prioritize broad compatibility over peak throughput. To optimize your deployment, you must adjust the `sysctl.conf` configurations. The `net.core.somaxconn` parameter dictates the maximum number of queued connections allowed on a single socket. Increasing this mitigates dropped SYN packets during burst traffic. Similarly, adjusting the `net.ipv4.tcp_max_syn_backlog` ensures the kernel memory buffers can accommodate massive simultaneous handshakes.

sudo sysctl -w net.core.somaxconn=65535
sudo sysctl -w net.ipv4.tcp_max_syn_backlog=16384
sudo sysctl -w net.ipv4.tcp_keepalive_time=300

Furthermore, standard file descriptor limits (`ulimit`) are often severely constrained for database and search operations. Modern applications maintain numerous persistent database connections and log file streams. Modifying `/etc/security/limits.conf` to increase the soft and hard limits for the `root` and `docker` system users dramatically enhances stability, preventing the infamous ‘Too many open files’ fatal exception during high-load scenarios.

Finally, disk I/O performance directly dictates the responsiveness of persistent volumes mapping to Postgres, Redis, or application cache layers. Switching the I/O scheduler to `mq-deadline` or `none` on NVMe storage bypasses unnecessary rotational latency optimizations, feeding data directly to the hardware controller. By combining aggressive network queuing, expansive file handler limits, and streamlined disk I/O protocols, your deployment is guaranteed to achieve enterprise-grade resilience and sub-millisecond local network response times.

In addition to kernel tuning, implementing a comprehensive monitoring strategy is paramount. Prometheus and Grafana should be deployed alongside your primary applications to scrape metrics endpoint data. Monitoring CPU wait times (iowait), memory paging rates, and Docker container CPU throttling provides actionable intelligence before system failure occurs. For logging, the ELK stack (Elasticsearch, Logstash, Kibana) or a lightweight alternative like Promtail and Loki can ingest Nginx access logs and application stderr/stdout streams, enabling rapid anomaly detection and forensic analysis during security incidents.

By rigorously applying these foundational Linux engineering principles, your self-hosted infrastructure will routinely outperform managed SaaS equivalents while maintaining absolute data sovereignty and minimizing recurring operational expenses.