Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-03-04 06:47:25 +08:00
Code Issues Packages Projects Releases Wiki Activity

4.9.3-debian-10-r48 release

Browse Source
This commit is contained in:
Bitnami Bot
2021-02-09 10:20:25 +00:00
parent 8e8b30643d
commit 0f27202b19
2 changed files with 6 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bitnami/parse/4/debian-10/Dockerfile
View File

@@ -15,12 +15,10 @@ RUN bitnami-pkg install mongodb-client-4.4.3-0 --checksum 0e76516960a83631bd6a55
RUN bitnami-pkg install tini-0.19.0-1 --checksum 9b1f1c095944bac88a62c1b63f3bff1bb123aa7ccd371c908c0e5b41cec2528d
RUN bitnami-pkg unpack parse-4.9.3-0 --checksum 06542d1d41c71615eb028ab06b14c9c0b2bb86cf44644960337a82c8c67fd34e
RUN bitnami-pkg install gosu-1.12.0-2 --checksum 4d858ac600c38af8de454c27b7f65c0074ec3069880cb16d259a6e40a46bbc50
RUN apt-get update && apt-get upgrade -y && \
rm -r /var/lib/apt/lists /var/cache/apt/archives
COPY rootfs /
ENV BITNAMI_APP_NAME="parse" \
BITNAMI_IMAGE_VERSION="4.9.3-debian-10-r47" \
BITNAMI_IMAGE_VERSION="4.9.3-debian-10-r48" \
MONGODB_HOST="mongodb" \
MONGODB_PASSWORD="" \
MONGODB_PORT_NUMBER="27017" \

10
bitnami/parse/README.md
View File

@@ -48,7 +48,7 @@ Non-root container images add an extra layer of security and are generally recom
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/).
* [`4`, `4-debian-10`, `4.9.3`, `4.9.3-debian-10-r47`, `latest` (4/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-parse/blob/4.9.3-debian-10-r47/4/debian-10/Dockerfile)
* [`4`, `4-debian-10`, `4.9.3`, `4.9.3-debian-10-r48`, `latest` (4/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-parse/blob/4.9.3-debian-10-r48/4/debian-10/Dockerfile)
Subscribe to project updates by watching the [bitnami/parse GitHub repo](https://github.com/bitnami/bitnami-docker-parse).
@@ -81,7 +81,7 @@ If you want to run the application manually instead of using docker-compose, the
$ docker network create parse_network
```
2. Start a MongoDB database in the network generated:
2. Start a MongoDB® database in the network generated:
```console
$ docker run -d --name mongodb --net=parse_network bitnami/mongodb
@@ -101,7 +101,7 @@ Then you can access your application at http://your-ip/parse
If you remove the container all your data and configurations 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 volume at the `/bitnami` path. Additionally you should mount a volume for [persistence of the MongoDB data](https://github.com/bitnami/bitnami-docker-mongodb#persisting-your-database).
For persistence you should mount a volume at the `/bitnami` path. Additionally you should mount a volume for [persistence of the MongoDB® data](https://github.com/bitnami/bitnami-docker-mongodb#persisting-your-database).
The above examples define docker volumes namely `mongodb_data` and `parse_data`. The Parse application state will persist as long as these volumes are not removed.
@@ -136,7 +136,7 @@ In this case you need to specify the directories to mount on the run command. Th
$ docker network create parse-tier
```
2. Create a MongoDB container with host volume:
2. Create a MongoDB® container with host volume:
```console
$ docker run -d --name mongodb \
@@ -177,7 +177,7 @@ Bitnami provides up-to-date versions of Mongodb and Parse, including security pa
$ rsync -a /path/to/parse-persistence /path/to/parse-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)
```
Additionally, [snapshot the MongoDB data](https://github.com/bitnami/bitnami-docker-mongodb#step-2-stop-and-backup-the-currently-running-container)
Additionally, [snapshot the MongoDB® data](https://github.com/bitnami/bitnami-docker-mongodb#step-2-stop-and-backup-the-currently-running-container)
You can use these snapshots to restore the application state should the upgrade fail.