What it is

Frappe Docker is the official container setup for Frappe applications, including ERPNext, CRM, Helpdesk, and other apps built on the Frappe framework. It lives in the self-hosted business software ecosystem, where organizations need a repeatable way to package, run, and operate web applications without depending on a vendor-hosted service. The project supplies Docker images, Docker Compose configurations, and documentation so teams can run Frappe applications on their own infrastructure.

The problem it solves is the gap between the Frappe application stack and a reproducible container deployment. The repository gives a quick demo setup, a base production compose file, and documentation for production use. It also supports building custom app images, which helps teams deploy Frappe-based software beyond the standard ERPNext, CRM, and Helpdesk applications.

Key capabilities

• Provides Docker images and Docker Compose configurations for running Frappe applications, including ERPNext, CRM, Helpdesk, and other Frappe apps.
• Offers a disposable demo setup through the pwd.yml compose file for short-lived evaluation before a production deployment is planned.
• Supports production deployment through the base compose.yaml file and overrides for common deployment patterns.
• Includes documentation for deployment methods, container setup, production operation, development workflows, and ARM64 notes.
• Supports custom application images and development configurations, including a VS Code devcontainer example.

Who uses it and how

• Teams evaluating ERPNext, CRM, or Helpdesk can start with the demo environment, wait for the create-site container, and open port 8080 with Administrator and admin credentials.
• Self-hosters can use the base compose file, overrides, and production documentation to shape a deployment for their own infrastructure.
• Developers building custom Frappe apps can use the images directory and development configuration to create container images with their own code.
• Operators can follow the operations documentation for running the stack after the initial containers are started.

Getting started

The README lists Docker, Docker Compose v2, and git as prerequisites. The quick start is to clone the frappe_docker repository, run the pwd.yml compose file, wait for the site to be created, and open the demo on port 8080.

When to use it — and when not to

Frappe Docker is useful when a team wants to self-host Frappe applications and needs an official container path for development, demonstration, and production deployment. It is not a hosted service, so teams must still operate the deployment themselves. The demo setup is disposable and cannot install custom apps, so production use should rely on the production documentation and compose overrides.

frappe_docker/
├── docs/                 # Complete documentation
├── overrides/            # Docker Compose configurations for different scenarios
├── compose.yaml          # Base Compose File for production setups
├── pwd.yml               # Single Compose File for quick disposable demo
├── images/               # Dockerfiles for building Frappe images
├── development/          # Development environment configurations
├── devcontainer-example/ # VS Code devcontainer setup
└── resources/            # Helper scripts and configuration templates

git clone https://github.com/frappe/frappe_docker
cd frappe_docker

docker compose -f pwd.yml up -d