No description or website provided.
Switch branches/tags
3.0.0-ol-7-r23 3.0.0-ol-7-r22 3.0.0-ol-7-r21 3.0.0-ol-7-r20 3.0.0-ol-7-r19 3.0.0-ol-7-r18 3.0.0-ol-7-r17 3.0.0-ol-7-r16 3.0.0-ol-7-r15 3.0.0-ol-7-r14 3.0.0-ol-7-r13 3.0.0-ol-7-r12 3.0.0-ol-7-r11 3.0.0-ol-7-r10 3.0.0-ol-7-r9 3.0.0-ol-7-r8 3.0.0-ol-7-r7 3.0.0-ol-7-r6 3.0.0-ol-7-r5 3.0.0-ol-7-r4 3.0.0-ol-7-r3 3.0.0-ol-7-r2 3.0.0-ol-7-r1 3.0.0-ol-7-r0 3.0.0-debian-9-r10 3.0.0-debian-9-r9 3.0.0-debian-9-r8 3.0.0-debian-9-r7 3.0.0-debian-9-r6 3.0.0-debian-9-r5 3.0.0-debian-9-r4 3.0.0-debian-9-r3 3.0.0-debian-9-r2 3.0.0-debian-9-r1 3.0.0-debian-9-r0 2.8.4-ol-7-r14 2.8.4-ol-7-r13 2.8.4-ol-7-r12 2.8.4-ol-7-r11 2.8.4-ol-7-r10 2.8.4-ol-7-r9 2.8.4-ol-7-r8 2.8.4-ol-7-r7 2.8.4-ol-7-r6 2.8.4-ol-7-r5 2.8.4-ol-7-r4 2.8.4-ol-7-r3 2.8.4-ol-7-r2 2.8.4-ol-7-r1 2.8.4-ol-7-r0 2.8.4-debian-9-r8 2.8.4-debian-9-r7 2.8.4-debian-9-r6 2.8.4-debian-9-r5 2.8.4-debian-9-r4 2.8.4-debian-9-r3 2.8.4-debian-9-r2 2.8.4-debian-9-r1 2.8.4-debian-9-r0 2.8.3-ol-7-r5 2.8.3-ol-7-r4 2.8.3-ol-7-r3 2.8.3-ol-7-r2 2.8.3-ol-7-r1 2.8.3-ol-7-r0 2.8.3-debian-9-r2 2.8.3-debian-9-r1 2.8.3-debian-9-r0 2.8.2-r1 2.8.2-r0 2.8.2-ol-7-r33 2.8.2-ol-7-r32 2.8.2-ol-7-r31 2.8.2-ol-7-r30 2.8.2-ol-7-r29 2.8.2-ol-7-r28 2.8.2-ol-7-r27 2.8.2-ol-7-r26 2.8.2-ol-7-r25 2.8.2-ol-7-r24 2.8.2-ol-7-r23 2.8.2-ol-7-r22 2.8.2-ol-7-r21 2.8.2-ol-7-r20 2.8.2-ol-7-r19 2.8.2-ol-7-r18 2.8.2-ol-7-r17 2.8.2-ol-7-r16 2.8.2-ol-7-r15 2.8.2-ol-7-r14 2.8.2-ol-7-r13 2.8.2-ol-7-r12 2.8.2-ol-7-r11 2.8.2-ol-7-r10 2.8.2-ol-7-r9 2.8.2-ol-7-r8 2.8.2-ol-7-r7 2.8.2-ol-7-r6 2.8.2-ol-7-r5 2.8.2-ol-7-r4
Nothing to show
Clone or download
carrodher Merge pull request #45 from bitnami/remove_debian_8
Removed Debian 8 from root version folders
Latest commit c8d6586 Sep 21, 2018


What is Parse?

Parse Server is an open source version of the Parse backend that can be deployed to any infrastructure that can run Node.js.

Looking for Parse + Parse Dashboard?

We also provide a Docker Image for Parse Dashboard. Parse Dashboard is a standalone dashboard for managing your Parse apps. You can find it at:

Bitnami Parse Dashboard


Docker Compose

$ curl -sSL > docker-compose.yml
$ docker-compose up -d

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.
  • Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
  • Bitnami images are built on CircleCI and automatically pushed to the Docker Hub.
  • All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.

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.

Supported tags and respective Dockerfile links

NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

Subscribe to project updates by watching the bitnami/parse GitHub repo.


To run this application you need Docker Engine 1.10.0. Docker Compose is recomended with a version 1.6.0 or later.

How to use this image

Run Parse with a Database Container

Running Parse with a database server is the recommended way. You can either use docker-compose or run the containers manually.

Run the application using Docker Compose

This is the recommended way to run Parse. You can use the following docker compose template:

version: '2'

    image: 'bitnami/mongodb:latest'
      - 'mongodb_data:/bitnami'
    image: 'bitnami/parse:latest'
      PARSE_HOST: your_host
      - '1337:1337'
      - 'parse_data:/bitnami'
      - mongodb
    driver: local
    driver: local

Run the application manually

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

  1. Create a new network for the application and the database:
$ docker network create parse_network
  1. Start a MongoDB database in the network generated:
$ docker run -d --name mongodb --net=parse_network bitnami/mongodb

Note: You need to give the container a name in order to Parse to resolve the host

  1. Run the Parse container:
$ docker run -d -p 1337:1337 --name parse --net=parse_network bitnami/parse

Then you can access your application at http://your-ip/parse

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.

For persistence you should mount a volume at the /bitnami path. Additionally you should mount a volume for persistence of the MongoDB data.

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.

To avoid inadvertent removal of these volumes you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

Mount host directories as data volumes with Docker Compose

This requires a minor change to the docker-compose.yml template previously shown:

version: '2'

    image: 'bitnami/mongodb:latest'
      - '/path/to/your/local/mongodb_data:/bitnami'
    image: bitnami/parse:latest
      - mongodb
      - 1337:1337
      - '/path/to/parse-persistence:/bitnami'

Mount host directories as data volumes using the Docker command line

In this case you need to specify the directories to mount on the run command. The process is the same than the one previously shown:

  1. Create a network (if it does not exist):
$ docker network create parse-tier
  1. Create a MongoDB container with host volume:
$ docker run -d --name mongodb \
  --net parse-tier \
  --volume /path/to/mongodb-persistence:/bitnami \

Note: You need to give the container a name in order to Parse to resolve the host

  1. Run the Parse container:
$ docker run -d --name parse -p 1337:1337 \
  --net parse-tier \
  --volume /path/to/parse-persistence:/bitnami \

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

  1. Get the updated images:
$ docker pull bitnami/parse:latest
  1. Stop your container
  • For docker-compose: $ docker-compose stop parse
  • For manual execution: $ docker stop parse
  1. Take a snapshot of the application state
$ rsync -a /path/to/parse-persistence /path/to/parse-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

Additionally, snapshot the MongoDB data

You can use these snapshots to restore the application state should the upgrade fail.

  1. Remove the currently running container
  • For docker-compose: $ docker-compose rm parse
  • For manual execution: $ docker rm parse
  1. Run the new image
  • For docker-compose: $ docker-compose up parse
  • For manual execution (mount the directories if needed): docker run --name parse bitnami/parse:latest


Environment variables

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. If you want to add a new environment variable:

  • For docker-compose add the variable name and value under the application section:
  image: bitnami/parse:latest
    - 1337:1337
    - PARSE_HOST=my_host
    - 'parse_data:/bitnami'
    - mongodb
  • For manual execution add a -e option with each variable and value:
 $ docker run -d -e PARSE_HOST=my_host -p 1337:1337 --name parse -v /your/local/path/bitnami/parse:/bitnami --network=parse_network bitnami/parse

Available variables:

  • PARSE_HOST: Parse server host. Default:
  • PARSE_PORT_NUMBER_NUMBER: Parse server port. Default: 1337
  • PARSE_MOUNT_PATH: Parse server mount path. Default: /parse
  • PARSE_APP_ID: Parse server App ID. Default: myappID
  • PARSE_MASTER_KEY: Parse server Master Key: mymasterKey
  • MONGODB_HOST: Hostname for Mongodb server. Default: mongodb
  • MONGODB_PORT_NUMBER: Port used by Mongodb server. Default: 27017


We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.


If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

  • Host OS and version
  • Docker version (docker version)
  • Output of docker info
  • Version of this container (echo $BITNAMI_IMAGE_VERSION inside the container)
  • The command you used to run the container, and any relevant output you saw (masking any sensitive information)


Copyright 2016-2018 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.