Last changed
docker pull cgr.dev/chainguard/harbor-core
Need access to a specific version? Contact us.
Get notified of upcoming product changes, critical vulnerability notifications and patches and more.
Sign InA Wolf-based image for Harbor - an open-source container registry with policies and RBAC, vulnerability scans, and provides trusted image signing.
Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.
This image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard registry.
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:
Now that we've added the repository, we can deploy Harbor!:
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:
Afterwards, edit values.yml
and substitute in Chainguard's images/tags. For instance, for harbor-core
, the following changes should be made:
And then deploy after configuration:
For more information on deploying Harbor via Helm, see the official documentation here.
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:
Then run the following in the terminal:
Now you're up and running with Harbor powered by Chainguard images!
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:
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:
Tag Wolfi using the registry and project path (library
is created by default):
And finally, push Wolfi to the registry!:
Wolfi is now being pushed to the registry and will be viewable in the portal.
If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.
Chainguard Images are a collection of container images designed for security and minimalism.
Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.
The main features of Chainguard Images include:
-dev
VariantsAs mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev
variant which does include a shell and package manager.
Although the -dev
image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev
variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.
That being said, it’s worth noting that -dev
variants of Chainguard Images are completely fine to run in production environments. After all, the -dev
variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.
To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:
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 agreementA FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.