public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-18 01:42:21 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/parse] Release 9.4.1-debian-12-r0 (#91226)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-03-04 03:20:18 +01:00
committed by GitHub
parent f326dedba2
commit 5c4ba4ed48
2 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/parse/9/debian-12/Dockerfile
+4 -4
View File
@@ -7,13 +7,13 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-03-02T12:13:34Z" \
org.opencontainers.image.created="2026-03-04T01:59:47Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/parse/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/parse" \
org.opencontainers.image.title="parse" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="9.4.0"
org.opencontainers.image.version="9.4.1"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@@ -31,7 +31,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
"python-3.14.3-9-linux-${OS_ARCH}-debian-12" \
"node-24.14.0-0-linux-${OS_ARCH}-debian-12" \
"mongodb-shell-2.7.0-0-linux-${OS_ARCH}-debian-12" \
"parse-9.4.0-0-linux-${OS_ARCH}-debian-12" \
"parse-9.4.1-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -50,7 +50,7 @@ RUN uninstall_packages curl
COPY rootfs /
RUN /opt/bitnami/scripts/parse/postunpack.sh
ENV APP_VERSION="9.4.0" \
ENV APP_VERSION="9.4.1" \
BITNAMI_APP_NAME="parse" \
IMAGE_REVISION="0" \
PATH="/opt/bitnami/python/bin:/opt/bitnami/node/bin:/opt/bitnami/mongodb/bin:/opt/bitnami/parse/bin:$PATH"
bitnami/parse/README.md
+15 -15
View File
@@ -5,7 +5,7 @@
[Overview of Parse Server](https://parseplatform.org/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## <a id="tl-dr"></a> TL;DR
## TL;DR
```console
docker run --name parse bitnami/parse:latest
@@ -13,7 +13,7 @@ docker run --name parse bitnami/parse:latest
You can find the default credentials and available configuration options in the [Environment Variables](#environment-variables) section.
## <a id="why-use-bitnami-secure-images"></a> Why use Bitnami Secure Images?
## Why use Bitnami Secure Images?
Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
@@ -30,27 +30,27 @@ Each image comes with valuable security metadata. You can view the metadata in [
If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy).
## <a id="how-to-deploy-in-kubernetes"></a> How to deploy Parse Server in Kubernetes?
## How to deploy Parse Server 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 Parse Server Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/parse).
## <a id="why-non-root"></a> 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://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).
## <a id="supported-tags"></a> 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://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
## <a id="how-to-use-this-image"></a> How to use this image
## How to use this image
### <a id="run-parse-with-a-database-container"></a> Run Parse with a Database Container
### Run Parse with a Database Container
#### Run the application using Docker Compose
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/parse).
### <a id="persisting-your-application"></a> Persisting your application
### Persisting your application
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.
@@ -62,7 +62,7 @@ To avoid inadvertent removal of these volumes you can [mount host directories as
> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
## <a id="upgrade-this-application"></a> Upgrade this application
## Upgrade this application
Bitnami provides up-to-date versions of Mongodb and Parse, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the Parse container. For the Mongodb upgrade see <https://github.com/bitnami/containers/tree/main/bitnami/mongodb#user-content-upgrade-this-image>
@@ -97,11 +97,11 @@ Bitnami provides up-to-date versions of Mongodb and Parse, including security pa
- For docker-compose: `$ docker-compose up parse`
- For manual execution (mount the directories if needed): `docker run --name parse bitnami/parse:latest`
## <a id="configuration"></a> Configuration
## Configuration
The following section describes the supported environment variables
### <a id="environment-variables"></a> Environment variables
### Environment variables
The following tables list the main variables you can set.
@@ -142,7 +142,7 @@ The following tables list the main variables you can set.
When you start the parse image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line.
### <a id="how-to-deploy-your-cloud-functions-with-parse-cloud-code?"></a> How to deploy your Cloud functions with Parse Cloud Code?
### How to deploy your Cloud functions with Parse Cloud Code?
You can use Cloud Code to run a piece of code in your Parse Server instead of the user's mobile devices. To run your Cloud functions using this image, follow the steps below:
@@ -164,13 +164,13 @@ EOF
Find more information about Cloud Code and Cloud functions in the [official documentation](https://docs.parseplatform.org/cloudcode/guide/).
### <a id="fips-configuration"></a> FIPS configuration in Bitnami Secure Images
### FIPS configuration in Bitnami Secure Images
The Bitnami Parse Server Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:
- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.
## <a id="notable-changes"></a> Notable Changes
## Notable Changes
### 4.9.3
@@ -185,7 +185,7 @@ The Bitnami Parse Server Docker image from the [Bitnami Secure Images](https://g
- The Parse container has been migrated to a non-root user approach. Previously the container ran as the `root` user and the Parse daemon was started as the `parse` user. From now on, both the container and the Parse daemon run as user `1001`. As a consequence, the data directory must be writable by that user. You can revert this behavior by changing `USER 1001` to `USER root` in the Dockerfile.
## <a id="license"></a> License
## License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.