0.13.1-debian-10-r219 release
This commit is contained in:
Bitnami Bot
parent
3e34ea5899
commit
adc1020c32
|
|
@ -16,7 +16,7 @@ RUN chmod g+rwX /opt/bitnami
|
|||
COPY rootfs /
|
||||
RUN /opt/bitnami/scripts/chartmuseum/postunpack.sh
|
||||
ENV BITNAMI_APP_NAME="chartmuseum" \
|
||||
BITNAMI_IMAGE_VERSION="0.13.1-debian-10-r218" \
|
||||
BITNAMI_IMAGE_VERSION="0.13.1-debian-10-r219" \
|
||||
PATH="/opt/bitnami/common/bin:/opt/bitnami/chartmuseum/bin:$PATH"
|
||||
|
||||
USER 1001
|
||||
|
|
|
|||
|
|
@ -1,16 +1,18 @@
|
|||
# What is chartmuseum?
|
||||
# ChartMuseum packaged by Bitnami
|
||||
|
||||
ChartMuseum is an open-source, easy to deploy, Helm Chart Repository server.
|
||||
## What is ChartMuseum?
|
||||
|
||||
[https://github.com/helm/chartmuseum](https://github.com/helm/chartmuseum)
|
||||
> ChartMuseum is an open-source, easy to deploy, Helm Chart Repository server.
|
||||
|
||||
# TL;DR
|
||||
[Overview of ChartMuseum](https://github.com/helm/chartmuseum)
|
||||
|
||||
## TL;DR
|
||||
|
||||
```console
|
||||
$ docker run --name chartmuseum bitnami/chartmuseum:latest
|
||||
```
|
||||
|
||||
# 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.
|
||||
|
|
@ -21,20 +23,20 @@ $ docker run --name chartmuseum bitnami/chartmuseum:latest
|
|||
|
||||
> This [CVE scan report](https://quay.io/repository/bitnami/chartmuseum?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.
|
||||
|
||||
# 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/).
|
||||
|
||||
|
||||
* [`0`, `0-debian-10`, `0.13.1`, `0.13.1-debian-10-r218`, `latest` (0/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-chartmuseum/blob/0.13.1-debian-10-r218/0/debian-10/Dockerfile)
|
||||
* [`0`, `0-debian-10`, `0.13.1`, `0.13.1-debian-10-r219`, `latest` (0/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-chartmuseum/blob/0.13.1-debian-10-r219/0/debian-10/Dockerfile)
|
||||
|
||||
Subscribe to project updates by watching the [bitnami/chartmuseum GitHub repo](https://github.com/bitnami/bitnami-docker-chartmuseum).
|
||||
|
||||
# Get this image
|
||||
## Get this image
|
||||
|
||||
The recommended way to get the Bitnami chartmuseum Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/chartmuseum).
|
||||
|
||||
|
|
@ -54,11 +56,11 @@ If you wish, you can also build the image yourself.
|
|||
$ docker build -t bitnami/chartmuseum:latest 'https://github.com/bitnami/bitnami-docker-chartmuseum.git#master:0/debian-10'
|
||||
```
|
||||
|
||||
# Configuring this image
|
||||
## Configuring this image
|
||||
|
||||
This image allows all the configuration explained on the [ChartMuseum web](https://chartmuseum.com/docs/#configuration) setting them by environment variables.
|
||||
|
||||
# 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.
|
||||
|
||||
|
|
@ -82,7 +84,7 @@ chartmuseum:
|
|||
|
||||
> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
|
||||
|
||||
# Using TLS certificates
|
||||
## Using TLS certificates
|
||||
|
||||
To configure ChartMuseum to enable TLS for communications, you can should mount your certificates under the path `/etc/harbor/ssl/chartmuseum`. Additionally, set the following environment variables to match your configuration:
|
||||
|
||||
|
|
@ -91,21 +93,21 @@ To configure ChartMuseum to enable TLS for communications, you can should mount
|
|||
|
||||
Should you want to add any custom CA certificate to trust, simply mount the files under the path `/harbor_cust_cert`.
|
||||
|
||||
# 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 chartmuseum-network --driver bridge
|
||||
```
|
||||
|
||||
### Step 2: Launch the chartmuseum container within your network
|
||||
#### Step 2: Launch the chartmuseum container within your network
|
||||
|
||||
Use the `--network <NETWORK>` argument to the `docker run` command to attach the container to the `chartmuseum-network` network.
|
||||
|
||||
|
|
@ -113,18 +115,18 @@ Use the `--network <NETWORK>` argument to the `docker run` command to attach the
|
|||
$ docker run --name chartmuseum-node1 --network chartmuseum-network bitnami/chartmuseum: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
|
||||
|
||||
To configure ChartMuseum you can use all the available parameters setting them through environment variables.
|
||||
The possible environment variables are explained [here](https://chartmuseum.com/docs/#configuration).
|
||||
They are equivalent to the command-line option using uppercase and separating the words with `_` instead of `-`.
|
||||
For example, the env var `STORAGE_AMAZON_BUCKET` can be used to set the command-line parameter `--storage-amazon-bucket`.
|
||||
|
||||
# Logging
|
||||
## Logging
|
||||
|
||||
The Bitnami chartmuseum Docker image sends the container logs to `stdout`. To view the logs:
|
||||
|
||||
|
|
@ -134,19 +136,19 @@ $ docker logs chartmuseum
|
|||
|
||||
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 chartmuseum, 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/chartmuseum:latest
|
||||
```
|
||||
|
||||
### Step 2: Stop the running container
|
||||
#### Step 2: Stop the running container
|
||||
|
||||
Stop the currently running container using the command
|
||||
|
||||
|
|
@ -154,13 +156,13 @@ Stop the currently running container using the command
|
|||
$ docker stop chartmuseum
|
||||
```
|
||||
|
||||
### Step 3: Remove the currently running container
|
||||
#### Step 3: Remove the currently running container
|
||||
|
||||
```console
|
||||
$ docker rm -v chartmuseum
|
||||
```
|
||||
|
||||
### Step 4: Run the new image
|
||||
#### Step 4: Run the new image
|
||||
|
||||
Re-create your container from the new image.
|
||||
|
||||
|
|
@ -168,11 +170,11 @@ Re-create your container from the new image.
|
|||
$ docker run --name chartmuseum bitnami/chartmuseum: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-chartmuseum/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-chartmuseum/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-chartmuseum/issues/new). For us to provide better support, be sure to include the following information in your issue:
|
||||
|
||||
|
|
@ -182,7 +184,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
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue