Bitnami package for Harbor Registryctl
What is Harbor Registryctl?
Harbor Registryctl is one of the main components of Harbor. Combined with the Harbor Registry, it is responsible for storing Docker images and processing pull/push operations.
Overview of Harbor Registryctl
TL;DR
This container is part of the Harbor solution that is primarily intended to be deployed in Kubernetes.
docker run --name harbor-registryctl bitnami/harbor-registryctl:latest
Why use Bitnami Images?
- Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
- With Bitnami images the latest bug fixes and features are available as soon as possible.
- Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
- All our images are based on minideb -a minimalist Debian based container image that gives you a small base container image and the familiarity of a leading Linux distribution- or scratch -an explicitly empty image-.
- All Bitnami images available in Docker Hub are signed with Notation. Check this post to know how to verify the integrity of the images.
- Bitnami container images are released on a regular basis with the latest distribution packages available.
Looking to use Harbor Registryctl in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.
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.
Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.
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 Registryctl 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
| Name | Description | Value |
|---|---|---|
HARBOR_REGISTRYCTL_BASE_DIR |
harbor-registryctl installation directory. | ${BITNAMI_ROOT_DIR}/harbor-registryctl |
HARBOR_REGISTRYCTL_STORAGE_DIR |
harbor-registry storage directory. | /storage |
HARBOR_REGISTRYCTL_DAEMON_USER |
harbor-registryctl system user. | harbor |
HARBOR_REGISTRYCTL_DAEMON_GROUP |
harbor-registryctl system group. | harbor |
Notable Changes
Starting January 16, 2024
- The
docker-compose.yamlfile 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 © 2024 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.