mirror of
https://github.com/bitnami/containers.git
synced 2026-03-16 14:57:44 +08:00
2.4.0-debian-10-r8 release
This commit is contained in:
Bitnami Bot
@@ -16,7 +16,7 @@ RUN chmod g+rwX /opt/bitnami
|
||||
COPY rootfs /
|
||||
RUN /opt/bitnami/scripts/harbor-adapter-clair/postunpack.sh
|
||||
ENV BITNAMI_APP_NAME="harbor-adapter-clair" \
|
||||
BITNAMI_IMAGE_VERSION="2.4.0-debian-10-r7" \
|
||||
BITNAMI_IMAGE_VERSION="2.4.0-debian-10-r8" \
|
||||
PATH="/opt/bitnami/harbor-adapter-clair/bin:/opt/bitnami/common/bin:$PATH"
|
||||
|
||||
EXPOSE 8080
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
# What is Harbor-Adapter-Clair?
|
||||
# Harbor Adapter Clair packaged by Bitnami
|
||||
|
||||
> The Harbor Scanner Adapter for Clair is a service that translates the Harbor scanning API into Clair API calls and allows Harbor to use Clair for providing vulnerability reports on images stored in Harbor registry as part of its vulnerability scan feature.
|
||||
>
|
||||
> Clair is an open source project for the static analysis of vulnerabilities in application containers.
|
||||
## What is Harbor Adapter Clair?
|
||||
|
||||
[https://github.com/goharbor/harbor-adapter-clair](https://github.com/goharbor/harbor-adapter-clair)
|
||||
> Harbor Adapter for Clair translates the Harbor API into Clair API calls and allows Harbor to use Clair for providing vulnerability reports on images as part of its vulnerability scan.
|
||||
|
||||
# TL;DR
|
||||
[Overview of Harbor Adapter Clair](https://github.com/goharbor/harbor-scanner-clair/releases)
|
||||
|
||||
## TL;DR
|
||||
|
||||
This container is part of the [Harbor solution](https://github.com/bitnami/charts/tree/master/bitnami/harbor) that is primarily intended to be deployed in Kubernetes. You can deploy Harbor solution and then enable this specific container with the command below:
|
||||
|
||||
@@ -16,7 +16,7 @@ $ curl -L https://github.com/bitnami/bitnami-docker-harbor-portal/archive/master
|
||||
$ docker-compose up
|
||||
```
|
||||
|
||||
# Why use Bitnami Images?
|
||||
## 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.
|
||||
@@ -27,26 +27,26 @@ $ docker-compose up
|
||||
|
||||
> This [CVE scan report](https://quay.io/repository/bitnami/harbor-adapter-clair?tab=tags) contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.
|
||||
|
||||
# How to deploy Harbor-Adapter-Clair in Kubernetes?
|
||||
## How to deploy Harbor-Adapter-Clair 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-Adapter-Clair Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/harbor-adapter-clair).
|
||||
|
||||
Bitnami containers can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters.
|
||||
|
||||
# Why use a non-root container?
|
||||
## 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](https://docs.bitnami.com/tutorials/work-with-non-root-containers/).
|
||||
|
||||
# Supported tags and respective `Dockerfile` links
|
||||
## 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](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
|
||||
|
||||
|
||||
* [`2`, `2-debian-10`, `2.4.0`, `2.4.0-debian-10-r7`, `latest` (2/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-harbor-adapter-clair/blob/2.4.0-debian-10-r7/2/debian-10/Dockerfile)
|
||||
* [`2`, `2-debian-10`, `2.4.0`, `2.4.0-debian-10-r8`, `latest` (2/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-harbor-adapter-clair/blob/2.4.0-debian-10-r8/2/debian-10/Dockerfile)
|
||||
|
||||
Subscribe to project updates by watching the [bitnami/harbor-adapter-clair GitHub repo](https://github.com/bitnami/bitnami-docker-harbor-adapter-clair).
|
||||
|
||||
# Get this image
|
||||
## Get this image
|
||||
|
||||
The recommended way to get the Bitnami Harbor-Adapter-Clair Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/harbor-adapter-clair).
|
||||
|
||||
@@ -66,7 +66,7 @@ If you wish, you can also build the image yourself.
|
||||
$ docker build -t bitnami/harbor-adapter-clair:latest 'https://github.com/bitnami/bitnami-docker-harbor-adapter-clair.git#master:2/debian-10'
|
||||
```
|
||||
|
||||
# Persisting your application
|
||||
## Persisting your application
|
||||
|
||||
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
|
||||
|
||||
@@ -88,21 +88,21 @@ harbor-adapter-clair:
|
||||
...
|
||||
```
|
||||
|
||||
# Connecting to other containers
|
||||
## Connecting to other containers
|
||||
|
||||
Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a different server running inside a container can easily be accessed by your application containers and vice-versa.
|
||||
|
||||
Containers attached to the same network can communicate with each other using the container name as the hostname.
|
||||
|
||||
## Using the Command Line
|
||||
### Using the Command Line
|
||||
|
||||
### Step 1: Create a network
|
||||
#### Step 1: Create a network
|
||||
|
||||
```console
|
||||
$ docker network create harbor-adapter-clair-network --driver bridge
|
||||
```
|
||||
|
||||
### Step 2: Launch the Harbor-Adapter-Clair container within your network
|
||||
#### Step 2: Launch the Harbor-Adapter-Clair container within your network
|
||||
|
||||
Use the `--network <NETWORK>` argument to the `docker run` command to attach the container to the `harbor-adapter-clair-network` network.
|
||||
|
||||
@@ -110,17 +110,17 @@ Use the `--network <NETWORK>` argument to the `docker run` command to attach the
|
||||
$ docker run --name harbor-adapter-clair-node1 --network harbor-adapter-clair-network bitnami/harbor-adapter-clair:latest
|
||||
```
|
||||
|
||||
### Step 3: Run another containers
|
||||
#### Step 3: Run another containers
|
||||
|
||||
We can launch another containers using the same flag (`--network NETWORK`) in the `docker run` command. If you also set a name to your container, you will be able to use it as hostname in your network.
|
||||
|
||||
# Configuration
|
||||
## Configuration
|
||||
|
||||
Harbor Adapter Clair 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](https://github.com/bitnami/charts/tree/master/bitnami/harbor) 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](https://github.com/goharbor/harbor-scanner-clair/blob/master/README.md).
|
||||
|
||||
# Logging
|
||||
## Logging
|
||||
|
||||
The Bitnami Harbor-Adapter-Clair Docker image sends the container logs to `stdout`. To view the logs:
|
||||
|
||||
@@ -130,19 +130,19 @@ $ docker logs harbor-adapter-clair
|
||||
|
||||
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
|
||||
|
||||
# Maintenance
|
||||
## Maintenance
|
||||
|
||||
## Upgrade this image
|
||||
### Upgrade this image
|
||||
|
||||
Bitnami provides up-to-date versions of Harbor-Adapter-Clair, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
|
||||
|
||||
### Step 1: Get the updated image
|
||||
#### Step 1: Get the updated image
|
||||
|
||||
```console
|
||||
$ docker pull bitnami/harbor-adapter-clair:latest
|
||||
```
|
||||
|
||||
### Step 2: Stop the running container
|
||||
#### Step 2: Stop the running container
|
||||
|
||||
Stop the currently running container using the command
|
||||
|
||||
@@ -150,13 +150,13 @@ Stop the currently running container using the command
|
||||
$ docker stop harbor-adapter-clair
|
||||
```
|
||||
|
||||
### Step 3: Remove the currently running container
|
||||
#### Step 3: Remove the currently running container
|
||||
|
||||
```console
|
||||
$ docker rm -v harbor-adapter-clair
|
||||
```
|
||||
|
||||
### Step 4: Run the new image
|
||||
#### Step 4: Run the new image
|
||||
|
||||
Re-create your container from the new image.
|
||||
|
||||
@@ -164,11 +164,11 @@ Re-create your container from the new image.
|
||||
$ docker run --name harbor-adapter-clair bitnami/harbor-adapter-clair:latest
|
||||
```
|
||||
|
||||
# Contributing
|
||||
## Contributing
|
||||
|
||||
We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/bitnami-docker-harbor-adapter-clair/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-harbor-adapter-clair/pulls) with your contribution.
|
||||
|
||||
# Issues
|
||||
## Issues
|
||||
|
||||
If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/bitnami-docker-harbor-adapter-clair/issues/new). For us to provide better support, be sure to include the following information in your issue:
|
||||
|
||||
@@ -178,7 +178,7 @@ If you encountered a problem running this container, you can file an [issue](htt
|
||||
- Version of this container
|
||||
- The command you used to run the container, and any relevant output you saw (masking any sensitive information)
|
||||
|
||||
# License
|
||||
## License
|
||||
|
||||
Copyright (c) 2021 Bitnami
|
||||
|
||||
|
||||
Reference in New Issue
Block a user