Harbor
Open-source container image registry with a web portal, projects and access control, replication and a Trivy-based vulnerability scanner, installed from an installer package that runs its services with Docker Compose.
| ID | harbor |
| Layer | registry |
| Version | v2.16.0 |
| Tiers | T1, T2, T3 |
| Requires | nothing |
| License | Apache-2.0 |
| Evidence | docs |
| Last verified | 2026-11-22 |
Choose it when
Section titled “Choose it when”- A registry with a web portal, projects and users, and built-in image vulnerability scanning is wanted: the vulnerability scanning page says Harbor provides static analysis of vulnerabilities in images through Trivy, enabled by installing with –with-trivy, and that other scanners can be connected.
- Harbor’s resource needs are acceptable: the prerequisites page gives a minimum of 2 CPU, 4 GB memory and 40 GB disk and a recommended 4 CPU, 8 GB and 160 GB, plus Docker Engine and Docker Compose on the host for the installer route.
Avoid it when
Section titled “Avoid it when”- Only a plain image store is needed and the host is small: the distribution-registry entry is the catalog’s lighter alternative; the resource figures above are the Harbor side of that comparison.
Caveats
Section titled “Caveats”- The installer route needs Docker Engine (version above 20.10) and Docker Compose (above 2.3, which the page says is part of Docker Engine) on the host (prerequisites page); install.sh checks that docker and either the docker compose plugin or docker-compose are installed (make/common.sh). Docker Engine is outside the catalog; Docker Compose is the catalog’s docker-compose entry (layer orchestration, tiers T1 and T2): a blueprint that needs it on the registry host lists it in the orchestration decision, not in the registry decision, and at a T3 orchestration floor the entry is not available, so the registry decision names Compose in existing or custom. docker-compose is not listed in requires because the same documentation also offers a Kubernetes route with Helm.
- Bundled services: the installer deploys its own PostgreSQL and cache, so postgresql and valkey are not listed in requires. External options: harbor.yml has external_database (the page says Harbor supports only PostgreSQL, the database must be created and the tables are generated at start) and external_redis (including Sentinel). The Helm high-availability page lists a highly available PostgreSQL 9.6 or newer and a highly available Redis as prerequisites that the user provides; that is the Kubernetes route, not the installer route of this entry.
- Security defaults: Harbor ships no certificates; the configuration pages say HTTP is acceptable only in air-gapped test or development environments and HTTPS is required otherwise. The initial administrator is admin with the password Harbor12345 unless harbor_admin_password is set, and the page says the database password must be changed for production.
- Vulnerability data: scanning needs the operator to carry the Trivy database files or an internal copy of the Trivy database artifacts (see runtime_downloads) and to repeat that whenever fresh vulnerability data is wanted; the Harbor documentation does not describe this procedure.
- No GPU workload documentation applies: Harbor stores and scans images and does not run models. Searched the whole docs directory of goharbor/website at the cited commit for gpu, cuda and nvidia on 2026-11-22: no match.
- No paid edition or license check was found in the documentation pages read (searched for enterprise edition, paid, subscription and license key).
Alternatives
Section titled “Alternatives”Carrying it in
Section titled “Carrying it in”No container images.
Packages:
- harbor-offline-installer-v2.16.0-amd64.tgz
Downloads at run time
Section titled “Downloads at run time”What the software tries to fetch while it runs, and how to stage it instead.
- Trivy vulnerability database (only when Harbor is installed with ./install.sh –with-trivy): the scanner is the harbor-scanner-trivy adapter v0.40.0 running Trivy v0.76.1 (Makefile at the Harbor tag). Trivy’s documentation says its databases are OCI artifacts in public registries (the vulnerability database trivy-db, the Java index trivy-java-db) that it downloads when it scans. Harbor’s prepare script (source at the tag) passes db_repository ghcr.io/aquasecurity/trivy-db and java_db_repository ghcr.io/aquasecurity/trivy-java-db unless harbor.yml sets others; the adapter README says its own default for the database is mirror.gcr.io/aquasec/trivy-db,ghcr.io/aquasecurity/trivy-db, and Trivy’s database page says Trivy tries mirror.gcr.io/aquasec first and then ghcr.io/aquasecurity; the three statements are recorded here and not reconciled. The template comment says the database is published about every 12 hours. Artifacts that exist (anonymous ghcr.io token, 2026-11-22): ghcr.io/aquasecurity/trivy-db with tags 1, 2 and latest (the tag 2 manifest, created 2026-11-21, has one layer db.tar.gz of type application/vnd.aquasec.trivy.db.layer.v1.tar+gzip, about 143 MB) and ghcr.io/aquasecurity/trivy-java-db with the tag 1 only. Trivy’s documentation uses trivy-db:2 and trivy-java-db:1 in its manual route.
- Route 1, manual cache (Trivy’s self-hosting page, with Harbor’s settings): on a connected host run oras pull ghcr.io/aquasecurity/trivy-db:2 (any tool that copies OCI artifacts works; the page names crane, ORAS and regclient), extract db.tar.gz to get trivy.db and metadata.json, and for Java scanning oras pull ghcr.io/aquasecurity/trivy-java-db:1 and extract javadb.tar.gz to get trivy-java.db and metadata.json. Carry the files and put them where the scanner container’s cache is: Trivy’s page puts the vulnerability files under the cache directory’s db subdirectory and the Java files under java-db; the adapter’s environment file (source at the tag) sets the cache directory to /home/scanner/.cache/trivy, and the compose template binds the host directory <data_volume>/trivy-adapter/trivy (/data/trivy-adapter/trivy by default) to it, so the files go to <data_volume>/trivy-adapter/trivy/db/ and <data_volume>/trivy-adapter/trivy/java-db/ (that mapping is from source code, not from a documentation page; prepare creates the directory with the ownership Harbor uses, and the files must be readable by that user). Then set trivy.skip_update: true (and trivy.skip_java_db_update: true when the Java files are staged) in harbor.yml, which the adapter turns into –skip-db-update and –skip-java-db-update. The adapter README says that with skip_update set and no database in place Trivy stops with the error that –skip-db-update cannot be specified on the first run. Refresh by repeating the carry; the database does not update itself in this route.
- Route 2, internal registry (Trivy’s self-hosting page): copy ghcr.io/aquasecurity/trivy-db:2 and ghcr.io/aquasecurity/trivy-java-db:1 into an internal OCI registry with crane, ORAS or regclient (the page warns that the layers have non-standard media types, application/vnd.aquasec.trivy.db.layer.v1.tar+gzip and application/vnd.aquasec.trivy.javadb.layer.v1.tar+gzip, which the serving registry must accept, and that the copies must be kept up to date), then set trivy.db_repository and trivy.java_db_repository in harbor.yml (the settings the template at the tag documents; the adapter’s variables are SCANNER_TRIVY_DB_REPOSITORY and SCANNER_TRIVY_JAVA_DB_REPOSITORY) and leave skip_update false. If the registry needs authentication, Trivy’s private registry authentication page applies (not read by this entry). Whether the Harbor documentation pages describe either route: they do not; the configuration page and the template still describe a trivy-offline.tar.gz archive; see the disagreements in airgap.notes.
License server
Section titled “License server”No license server is contacted.
Telemetry and outbound calls
Section titled “Telemetry and outbound calls”| What | How to turn it off |
|---|---|
| Trivy usage telemetry and version check, run by the Trivy scanner of Harbor (only with –with-trivy). Trivy’s documentation (v0.76.1) says Trivy collects anonymous usage data (an installation identifier that is a one-way hash of a machine fingerprint, the Trivy version, the operating system and a list of non-revealing scan options; no file paths, image names or scan results) and that Trivy also checks for updates and notices; both go to https://check.trivy.dev, described as optional and not needed for normal operation. In the Harbor network the request cannot succeed without access to that host. Whether the adapter at the shipped version passes the switches: read in the source of harbor-scanner-trivy v0.40.0 (not a documentation page), the Trivy command line the adapter builds (pkg/trivy/wrapper.go) contains neither –disable-telemetry nor –skip-version-check, the adapter’s README and source mention neither, and the adapter starts Trivy with the environment of its own process. Harbor v2.16.0 exposes no setting for them: the adapter’s environment file generated by prepare (make/photon/prepare/templates/trivy-adapter/env.jinja) and harbor.yml have no such key, and the Harbor documentation pages read do not mention them. Whether a Trivy run started by the adapter actually sends the telemetry was not tested. | Harbor v2.16.0 exposes no setting; block check.trivy.dev, which Trivy’s air-gap page calls entirely optional and not necessary for the normal operation of Trivy. For reference, Trivy documents –disable-telemetry and –skip-version-check (both are needed, because the two features share the request to check.trivy.dev and one flag alone does not stop it), settable on the command line, in its YAML configuration file or as environment variables, which Trivy’s configuration page names by adding the TRIVY_ prefix, upper-casing and replacing - with _ (TRIVY_DISABLE_TELEMETRY and TRIVY_SKIP_VERSION_CHECK follow from that rule and are not written out on a page). No Harbor or adapter page documents a way to set them in Harbor’s Trivy container, so this entry names no workaround; the adapter source shows that environment variables of the container reach Trivy, but how to add them to the container Harbor generates is not documented. |
| Java package lookups by the Trivy scanner of Harbor (only with –with-trivy): Trivy’s air-gap page (v0.76.1) says Trivy might call out to Maven Central (https://repo.maven.apache.org/maven2) or other remote repositories to identify Java packages during a vulnerability scan, and the comment in harbor.yml.tmpl at v2.16.0 says the offline_scan option prevents Trivy from sending API requests to identify dependencies; the template sets offline_scan: false. | trivy.offline_scan: true in harbor.yml (passed to the adapter as SCANNER_TRIVY_OFFLINE_SCAN by make/photon/prepare/templates/trivy-adapter/env.jinja); the template comment says to set it together with skip_update in an air-gapped environment and that fewer vulnerabilities might be detected. |
Offline behavior is documented but not verified. The Download the Harbor Installer page says the offline installer is for hosts without a connection to the internet and contains pre-built images, while the online installer downloads the images from Docker Hub; the page uses the generic file names harbor-offline-installer-version.tgz, whereas the release names its files per architecture. The file in airgap.packages is the offline installer of the release v2.16.0 for linux/amd64 (x86_64) hosts: the platform of every image inside is linux/amd64 (inspected). For arm64 hosts the release publishes harbor-offline-installer-v2.16.0-arm64.tgz (not inspected by this entry), and the release notes list full multi-architecture enablement for amd64 and arm64; the release has no installer for another CPU architecture, and the documentation pages read name no architecture. The online installers (harbor-online-installer-v2.16.0-amd64.tgz and -arm64.tgz) pull images from Docker Hub and are not listed. Verification files named by the release: for each of the four installers a .sigstore.json file (for example harbor-offline-installer-v2.16.0-amd64.tgz.sigstore.json) and one file named md5sum, which lists the md5 sums of the four installers; the documentation says an OpenPGP .asc file may be used with gpg, but the release publishes no .asc file, so the page and the release disagree. None of these verification files is listed in packages because the documentation does not name the files the release publishes. The contents of the amd64 offline installer (listed): harbor.v2.16.0.tar.gz (the image archive, loaded by install.sh with docker load), install.sh, prepare, common.sh, harbor.yml.tmpl and LICENSE. The image archive holds twelve images, which are not listed in images because the archive carries them; the compose template and the Makefile at the tag name the same repositories with the release tag: goharbor/harbor-core:v2.16.0, goharbor/harbor-portal:v2.16.0, goharbor/harbor-jobservice:v2.16.0, goharbor/harbor-registryctl:v2.16.0, goharbor/registry-photon:v2.16.0 (the registry), goharbor/harbor-db:v2.16.0 (PostgreSQL), goharbor/valkey-photon:v2.16.0 (the cache), goharbor/nginx-photon:v2.16.0 (the proxy in front), goharbor/harbor-log:v2.16.0, goharbor/trivy-adapter-photon:v2.16.0, goharbor/harbor-exporter:v2.16.0 and goharbor/prepare:v2.16.0. Services deployed by the compose template at the tag: log, registry, registryctl, postgresql, core, portal, jobservice, redis (running the valkey-photon image), proxy, plus trivy-adapter with –with-trivy (the default installation has no Trivy) and exporter when metric.enabled is true. The install steps are: extract the archive, copy harbor.yml.tmpl to harbor.yml and set at least hostname (not localhost or 127.0.0.1), configure HTTPS, run sudo ./install.sh [–with-trivy]. The documentation’s table of components says PostgreSQL 15.10 and Redis 7.2.6, while the compose template at the release tag runs goharbor/valkey-photon for the cache; this entry records both. The Harbor Makefile at the tag names the registry source version v2.8.3-patch-redis, so the registry inside Harbor is built from the distribution v2 line, not the v3 release of the distribution-registry entry. Other route, not a carry item of this entry: the Helm chart for Kubernetes (helm repo add harbor https://helm.goharbor.io); the documentation read gives no offline procedure for it, and the chart and the images it uses are not listed here. Outbound calls: the documented default outbound calls are the Trivy database download described in runtime_downloads, with the switch trivy.skip_update, and, described in telemetry, Trivy’s own version check and telemetry and its Java package lookups at Maven Central. No Harbor telemetry, analytics, usage statistics, phone-home or update-check documentation was found on 2026-11-22 (searched the pages of goharbor/website at the cited commit and the repository at the release tag; the matches were the opt-in distributed tracing and metrics settings, trace.enabled and metric.enabled, both off by default in harbor.yml; a search is not proof of absence); vet before adoption. Replication and proxy-cache projects reach external registries only when an administrator configures them; the pages read describe no default connection to an external registry. Proxy allow-list: the Harbor configuration page says that when Trivy is enabled behind a proxy, github.com, github-releases.githubusercontent.com and *.s3.amazonaws.com must be on the proxy’s allow-list; Trivy’s air-gap page lists mirror.gcr.io, googlecode.l.googleusercontent.com, ghcr.io and pkg-containers.githubusercontent.com as the hosts of its default database registries. Neither is needed when the database is staged by hand or comes from an internal registry. Other Trivy settings for a site without internet access: trivy.offline_scan: true (adapter –offline-scan; also listed in telemetry) stops Trivy from calling Maven Central to identify Java packages, possibly finding fewer vulnerabilities (Trivy air-gap page; the template comment says it is needed together with skip_update in an air-gapped environment). Misconfiguration scanning (trivy.security_check including config) uses the trivy-checks bundle, which Trivy’s page says is also an OCI artifact with an embedded fallback; Harbor’s default security_check is vuln, and Harbor exposes no setting for the checks repository. Trivy’s VEX Hub is fetched from GitHub (api.github.com, codeload.github.com) when VEX is configured; the adapter has a SCANNER_TRIVY_SKIP_VEX_REPO_UPDATE variable marked experimental, and Harbor’s environment file for the adapter does not set it. Disagreements between the pages about the Trivy database, recorded both ways and not resolved: (a) the Harbor configuration page and the harbor.yml template comment tell the operator to download trivy-offline.tar.gz and mount trivy.db and metadata.json, and name GitHub as the database source (with a 60 requests per hour anonymous limit and trivy.github_token to raise it); the aquasecurity/trivy-db repository’s GitHub releases list (API, 2026-11-22) ends with a release published 2023-02-08, so the operator has no such archive to carry, while Trivy’s own pages and the adapter’s defaults use the OCI artifacts described in runtime_downloads. (b) The configuration page gives the target as the file /home/scanner/.cache/trivy/db/trivy.db and the template comment as the directory /home/scanner/.cache/trivy/db; the adapter README gives the file path; the pages agree on the directory. (c) The Import Vulnerability Data page describes updating Clair, which the same page says was removed as default scanner in Harbor v2.2; it does not apply to Trivy.
Deeper skills
Section titled “Deeper skills”For running the tool itself, these skills go further than the catalog:
k8s-components-checkerin air-gapped/skills
Evidence
Section titled “Evidence”All values were read on 2026-11-22 from the pages in sources. The version v2.16.0 is the highest stable release (published 2026-11-10, not a prerelease). GitHub marks v2.15.5 (published 2026-11-12) as the latest release, because it is a later patch of the older 2.15 line; this entry follows v2.16.0, whose release publishes one offline installer per CPU architecture (amd64 and arm64) and whose notes list full multi-architecture enablement for amd64 and arm64. The Harbor documentation for a release is in the branch release-2.16.0 of goharbor/website (the page title reads Harbor v2.16.0 Documentation); the repository has no tag for it, so its pages are cited at commit 1ce1ac23f8d4969ce587b7ced8afb7954f76115d, the head of that branch on 2026-11-22. The Trivy pages are cited at the Trivy version that the Makefile at the Harbor tag names (TRIVYVERSION v0.76.1) and the adapter pages at the adapter version it names (TRIVYADAPTERVERSION v0.40.0). The entry author downloaded harbor-offline-installer-v2.16.0-amd64.tgz, compared its md5 sum (056a7e05842aeee148a853da1dc2eea7) with the md5sum file of the release, and listed its contents and the image names and platforms inside its image archive without running it; the arm64 installer was not downloaded. The offline behavior is documented but not verified: Harbor was not run. The tag lists and manifests at ghcr.io/v2/aquasecurity/trivy-db and trivy-java-db (the registry API; they need an anonymous pull token from https://ghcr.io/token?scope=repository:aquasecurity/trivy-db:pull and are therefore not in sources as links) were read with that token on 2026-11-22; the package pages in sources show the same repositories.
Sources:
- https://api.github.com/repos/goharbor/harbor/releases?per_page=10
- https://github.com/goharbor/harbor/releases/tag/v2.16.0
- https://api.github.com/repos/goharbor/harbor/releases/tags/v2.16.0
- https://github.com/goharbor/harbor/releases/download/v2.16.0/md5sum
- https://api.github.com/repos/goharbor/harbor/license
- https://github.com/goharbor/harbor/blob/v2.16.0/LICENSE
- https://github.com/goharbor/harbor/blob/v2.16.0/Makefile
- https://github.com/goharbor/harbor/blob/v2.16.0/make/harbor.yml.tmpl
- https://github.com/goharbor/harbor/blob/v2.16.0/make/install.sh
- https://github.com/goharbor/harbor/blob/v2.16.0/make/common.sh
- https://github.com/goharbor/harbor/blob/v2.16.0/make/photon/prepare/templates/docker_compose/docker-compose.yml.jinja
- https://github.com/goharbor/harbor/blob/v2.16.0/make/photon/prepare/templates/trivy-adapter/env.jinja
- https://github.com/goharbor/harbor/blob/v2.16.0/make/photon/prepare/utils/configs.py
- https://github.com/goharbor/website/blob/1ce1ac23f8d4969ce587b7ced8afb7954f76115d/docs/install-config/_index.md
- https://github.com/goharbor/website/blob/1ce1ac23f8d4969ce587b7ced8afb7954f76115d/docs/install-config/installation-prereqs.md
- https://github.com/goharbor/website/blob/1ce1ac23f8d4969ce587b7ced8afb7954f76115d/docs/install-config/download-installer.md
- https://github.com/goharbor/website/blob/1ce1ac23f8d4969ce587b7ced8afb7954f76115d/docs/install-config/run-installer-script.md
- https://github.com/goharbor/website/blob/1ce1ac23f8d4969ce587b7ced8afb7954f76115d/docs/install-config/configure-yml-file.md
- https://github.com/goharbor/website/blob/1ce1ac23f8d4969ce587b7ced8afb7954f76115d/docs/install-config/harbor-ha-helm.md
- https://github.com/goharbor/website/blob/1ce1ac23f8d4969ce587b7ced8afb7954f76115d/docs/administration/vulnerability-scanning/_index.md
- https://github.com/goharbor/website/blob/1ce1ac23f8d4969ce587b7ced8afb7954f76115d/docs/administration/vulnerability-scanning/import-vulnerability-data.md
- https://github.com/goharbor/website/blob/1ce1ac23f8d4969ce587b7ced8afb7954f76115d/docs/administration/vulnerability-scanning/pluggable-scanners.md
- https://github.com/goharbor/harbor-scanner-trivy/blob/v0.40.0/README.md
- https://github.com/goharbor/harbor-scanner-trivy/blob/v0.40.0/pkg/trivy/wrapper.go
- https://github.com/aquasecurity/trivy/blob/v0.76.1/docs/guide/advanced/air-gap.md
- https://github.com/aquasecurity/trivy/blob/v0.76.1/docs/guide/advanced/self-hosting.md
- https://github.com/aquasecurity/trivy/blob/v0.76.1/docs/guide/advanced/telemetry.md
- https://github.com/aquasecurity/trivy/blob/v0.76.1/docs/guide/configuration/db.md
- https://github.com/aquasecurity/trivy/blob/v0.76.1/docs/guide/configuration/others.md
- https://github.com/aquasecurity/trivy/blob/v0.76.1/docs/guide/configuration/index.md
- https://api.github.com/repos/aquasecurity/trivy-db/releases
- https://github.com/aquasecurity/trivy-db/pkgs/container/trivy-db
- https://github.com/aquasecurity/trivy-java-db/pkgs/container/trivy-java-db
Source of this page: skills/airgap-architect/catalog/components/harbor.toml.