Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-03-07 18:17:20 +08:00
Code Issues Packages Projects Releases Wiki Activity

0.9.0-debian-9-r2 release

Browse Source
This commit is contained in:
Bitnami Bot
2019-08-08 08:13:49 +00:00
parent 0119521c5a
commit 1b35fe76a8
2 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bitnami/chartmuseum/0/debian-9/Dockerfile
View File

@@ -1,4 +1,4 @@
FROM bitnami/minideb-extras-base:stretch-r323
FROM bitnami/minideb-extras-base:stretch-r324
LABEL maintainer "Bitnami <containers@bitnami.com>"
ENV BITNAMI_PKG_CHMOD="-R g+rwX" \
@@ -12,7 +12,7 @@ RUN . ./libcomponent.sh && component_unpack "chartmuseum" "0.9.0-1" --checksum b
COPY rootfs /
ENV BITNAMI_APP_NAME="chartmuseum" \
BITNAMI_IMAGE_VERSION="0.9.0-debian-9-r1" \
BITNAMI_IMAGE_VERSION="0.9.0-debian-9-r2" \
NAMI_PREFIX="/.nami" \
PATH="/opt/bitnami/chartmuseum/bin:$PATH"

12
bitnami/chartmuseum/README.md
View File

@@ -45,7 +45,7 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
* [`0-ol-7`, `0.9.0-ol-7-r0` (0/ol-7/Dockerfile)](https://github.com/bitnami/bitnami-docker-chartmuseum/blob/0.9.0-ol-7-r0/0/ol-7/Dockerfile)
* [`0-debian-9`, `0.9.0-debian-9-r1`, `0`, `0.9.0`, `0.9.0-r1`, `latest` (0/debian-9/Dockerfile)](https://github.com/bitnami/bitnami-docker-chartmuseum/blob/0.9.0-debian-9-r1/0/debian-9/Dockerfile)
* [`0-debian-9`, `0.9.0-debian-9-r2`, `0`, `0.9.0`, `0.9.0-r2`, `latest` (0/debian-9/Dockerfile)](https://github.com/bitnami/bitnami-docker-chartmuseum/blob/0.9.0-debian-9-r2/0/debian-9/Dockerfile)
Subscribe to project updates by watching the [bitnami/chartmuseum GitHub repo](https://github.com/bitnami/bitnami-docker-chartmuseum).
@@ -77,11 +77,11 @@ This image allows all the configuration explained on the [ChartMuseum web](https
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.
For persistence you should mount a directory at the `/bitnami` path. If the mounted directory is empty, it will be initialized on the first run.
For persistence you should mount a directory at the `/bitnami/data` path. If the mounted directory is empty, it will be initialized on the first run.
```bash
$ docker run \
-v /path/to/chartmuseum-persistence:/bitnami \
-v /path/to/chartmuseum-persistence:/bitnami/data \
bitnami/chartmuseum:latest
```
@@ -91,10 +91,14 @@ You can also do this with a minor change to the [`docker-compose.yml`](https://g
chartmuseum:
...
volumes:
- /path/to/chartmuseum-persistence:/bitnami
- /path/to/chartmuseum-persistence:/bitnami/data
...
```
# Using TLS certificates
To configure ChartMuseum to use TLS certificates you can mount a directory into `/bitnami/certs` containing the files `server.crt` and `server.key`.
# 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.