bitnami/harbor-core repository overview

⁠Bitnami Secure Image for Harbor Core

⁠What is Harbor Core?

Overview of Harbor Core⁠ Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

⁠TL;DR

This container is part of the Harbor solution⁠ that is primarily intended to be deployed in Kubernetes.

docker run --name harbor-core bitnami/harbor-core:latest

⁠Why use Bitnami Secure Images?

Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise OS Photon Linux⁠. Why choose BSI images?

• Hardened secure images of popular open source software with Near-Zero Vulnerabilities
• Vulnerability Triage & Prioritization with VEX Statements, KEV and EPSS Scores
• Compliance focus with FIPS, STIG, and air-gap options, including secure bill of materials (SBOM)
• Software supply chain provenance attestation through in-toto
• First class support for the internet’s favorite Helm charts

Each image comes with valuable security metadata. You can view the metadata in our public catalog here⁠. Note: Some data is only available with commercial subscriptions to BSI⁠.

If you are looking for our previous generation of images based on Debian Linux, please see the Bitnami Legacy registry⁠.

⁠How to deploy Harbor in Kubernetes?

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Harbor Chart GitHub repository⁠.

⁠Why use a non-root container?

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs⁠.

⁠Supported tags and respective Dockerfile links

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page⁠.

You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.

Subscribe to project updates by watching the bitnami/containers GitHub repo⁠.

⁠Configuration

Harbor Core is a component of the Harbor application. In order to get the Harbor application running on Kubernetes we encourage you to check the bitnami/harbor Helm chart⁠ and configure it using the options exposed in the values.yaml file.

For further information about the specific component itself, please refer to the source repository documentation⁠.

⁠Environment variables

⁠Customizable environment variables

⁠Read-only environment variables

⁠FIPS configuration in Bitnami Secure Images

The Bitnami Harbor Core Docker image from the Bitnami Secure Images⁠ catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:

• OPENSSL_FIPS: whether OpenSSL runs in FIPS mode or not. yes (default), no.

⁠Notable Changes

⁠Starting January 16, 2024

• The docker-compose.yaml file has been removed, as it was solely intended for internal testing purposes.

⁠Contributing

We'd love for you to contribute to this container. You can request new features by creating an issue⁠ or submitting a pull request⁠ with your contribution.

⁠Issues

If you encountered a problem running this container, you can file an issue⁠. For us to provide better support, be sure to fill the issue template.

⁠License

Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0⁠

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.