DirectorySecurity advisories
Sign in

Directory

harbor-trivy-adapter-fips logoFIPS

harbor-trivy-adapter-fips

Last changed
Sign in for updates

Get notified of upcoming product changes, critical vulnerability notifications and patches and more.

Sign in
Versions
Overview
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

A Wolf-based image for Harbor - an open-source container registry with policies and RBAC, vulnerability scans, and provides trusted image signing.

Download this Image

The image is available on cgr.dev:

docker pull cgr.dev/chainguard/harbor-registry:latest

Deploying Harbor with Helm

The easiest way to get up and running with Chainguard's Harbor images is via deployment with Harbor's official Helm chart.

To get started, we need to add Harbor's Helm repository:

helm repo add harbor https://helm.goharbor.io

Now that we've added the repository, we can deploy Harbor!:

helm install harbor harbor/harbor \
  --set core.image.repository=cgr.dev/chainguard/harbor-core,core.image.tag=latest \
  --set jobservice.image.repository=cgr.dev/chainguard/harbor-jobservice,jobservice.image.tag=latest \
  --set portal.image.repository=cgr.dev/chainguard/harbor-portal,portal.image.tag=latest \
  --set registry.registry.image.repository=cgr.dev/chainguard/harbor-registry,registry.registry.image.tag=latest \
  --set registry.registryctl.image.repository=cgr.dev/chainguard/harbor-registryctl,registry.registryctl.image.tag=latest \
  --set trivy.image.repository=cgr.dev/chainguard/harbor-trivy-adapter,trivy.image.tag=latest

You will need to override the image and tag values for each image like we've done here to point to Chainguard's Harbor images and tags.

Additionally, you may fetch Harbor's Helm chart after adding the repository and edit values directly without overriding them on installation:

helm fetch harbor/harbor --untar

Afterwards, edit values.yml and substitute in Chainguard's images/tags. For instance, for harbor-core, the following changes should be made:

core:
  ...
  image: cgr.dev/chainguard/harbor-core
  tag: latest
  ...

And then deploy after configuration:

helm install harbor .

For more information on deploying Harbor via Helm, see the official documentation here.

Deploying Harbor with Docker Compose

Harbor provides an online installer that can be retrieved from their releases on GitHub here.

Follow all of their steps for installation up until you've successfully generated your docker-compose.yml. At this point, you can swap the upstream images out for Chainguard's.

For instance, to switch out harbor-core with Chainguard's image, edit docker-compose.yml and make the following change:

services:
  ...
  core:
    image: cgr.dev/chainguard/harbor-core:latest
  ...

Then run the following in the terminal:

docker-compose up

Now you're up and running with Harbor powered by Chainguard images!

Usage

Now that you've deployed Harbor, the portal should be accessible on whatever host you've opted to use. For example, if configured to use localhost, the portal will be accessible at localhost:80 via HTTP or localhost:443 via HTTPS, if setup.

You may now login with the username and password you've set or via the default username and password, admin and Harbor12345. You'll be presented with several options, including the ability to create a new project in the registry.

Additionally, you can now login to the registry with Docker! To do so, open a terminal and run:

docker login localhost

Where localhost should be substituted with the hostname or external URL you've chosen for Harbor.

Now let's push an image using Chainguard's base container for Wolfi!

Pull Wolfi:

docker pull cgr.dev/chainguard/wolfi-base:latest

Tag Wolfi using the registry and project path (library is created by default):

docker tag cgr.dev/chainguard/wolfi-base:latest locahost/library/wolfi-base:latest

And finally, push Wolfi to the registry!:

docker push localhost/library/wolfi-base:latest

Wolfi is now being pushed to the registry and will be viewable in the portal.

Licenses

Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:

  • MIT

  • Apache-2.0

  • LGPL-2.1-or-later

  • MIT

  • MPL-2.0

For a complete list of licenses, please refer to this Image's SBOM.

Software license agreement 

Related images

Category
FIPS
registry

Products

Chainguard Images

© 2024 Chainguard, Inc.