harbor-log

packaged by Chainguard

Chainguard Container for harbor-log

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

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/harbor-log:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Deploying Harbor with Helm

You can deploy Chainguard's Harbor container images using Harbor's official Helm chart.

Create a values.yaml file with the following content, replacing ORGANIZATION with your Chainguard organization name:

portal:
  image:
    repository: cgr.dev/ORGANIZATION/harbor-portal
    tag: latest
core:
  image:
    repository: cgr.dev/ORGANIZATION/harbor-core
    tag: latest
jobservice:
  image:
    repository: cgr.dev/ORGANIZATION/harbor-jobservice
    tag: latest
registry:
  registry:
    image:
      repository: cgr.dev/ORGANIZATION/harbor-registry
      tag: latest
    extraEnvVars:
      - name: REGISTRY_REDIS_OPTIONS_ADDRS
        value: "[harbor-redis:6379]"
  controller:
    image:
      repository: cgr.dev/ORGANIZATION/harbor-registryctl
      tag: latest
trivy:
  image:
    repository: cgr.dev/ORGANIZATION/harbor-trivy-adapter
    tag: latest
database:
  internal:
    image:
      repository: cgr.dev/ORGANIZATION/harbor-db
      tag: latest
exporter:
  image:
    repository: cgr.dev/ORGANIZATION/harbor-exporter
    tag: latest
redis:
  internal:
    image:
      repository: cgr.dev/ORGANIZATION/harbor-redis
      tag: latest

Then add Harbor's Helm repository and deploy using the values file:

helm repo add harbor https://helm.goharbor.io
helm install harbor -f values.yaml harbor/harbor -n harbor --create-namespace

For more information on deploying Harbor via Helm, refer to the official documentation.

Deploying Harbor with Docker Compose

Harbor provides an online installer that can be retrieved from their Releases page on GitHub.

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 container images out for Chainguard's.

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

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

Then run the following in the terminal:

docker compose up

Now you're up and running with Harbor powered by Chainguard Containers.

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.

You may now log in 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 log in 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. Start by pulling the wolfi-base image:

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

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

docker tag cgr.dev/ORGANIZATION/wolfi-base:latest localhost/library/wolfi-base:latest

And finally, push Wolfi to the registry:

docker push localhost/library/wolfi-base:latest

After this image is pushed to the registry, it will be viewable in the Harbor portal.

Harbor Log

harbor-log is a centralized syslog collector for Harbor container registry. It runs rsyslog to collect logs from all Harbor components (core, jobservice, registry, etc.) over UDP and TCP on port 10514, routing them to /var/log/docker/<programname>.log with hourly logrotate rotation via cronie.

Harbor Log is used in Docker Compose and bare-metal Harbor deployments. The Harbor Helm chart does not deploy harbor-log — it uses pod-level stdout logging instead.

To use Chainguard's harbor-log in a Docker Compose deployment, update your docker-compose.yml:

services:
  log:
    image: cgr.dev/ORGANIZATION/harbor-log:latest
    privileged: true
    ports:
      - 10514:10514/udp
      - 10514:10514/tcp
    volumes:
      - /var/log/harbor:/var/log/docker

Or run it standalone for testing:

docker run -d --privileged \
  -p 10514:10514/udp \
  -p 10514:10514/tcp \
  -v /var/log/harbor:/var/log/docker \
  cgr.dev/ORGANIZATION/harbor-log:latest

Documentation and Resources

• Harbor Documentation
• Harbor Helm Chart
• Harbor GitHub
• Harbor Log Dockerfile

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.