epistemophiliac/frappe_docker
1
0
Fork 0
mirror of https://github.com/frappe/frappe_docker.git synced 2026-06-17 13:55:08 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
frappe_docker/docs/02-setup/03-start-setup.md
adithya 477376edc4 refactor: Moved md files back to docs 
Refactor can be considered later if needed.
2026-03-15 18:47:35 +05:30

2.4 KiB
Raw Blame History

title
Start Container

start Container

Once your compose file is ready, start all containers with a single command:

docker compose -p frappe -f compose.custom.yaml up -d

podman-compose --in-pod=1 --project-name frappe -f compose.custom.yaml up -d

The -p (or --project-name) flag names the project frappe, allowing you to easily reference and manage all containers together.

Create a site and install apps

Frappe is now running, but it's not yet configured. You need to create a site and install your apps.

Basic site creation

docker compose -p frappe exec backend bench new-site <sitename> --mariadb-user-host-login-scope='172.%.%.%'
docker compose -p frappe exec backend bench --site <sitename> install-app erpnext

podman exec -ti erpnext_backend_1 /bin/bash
bench new-site <sitename> --mariadb-user-host-login-scope='172.%.%.%'
bench --site <sitename> install-app erpnext

Replace <sitename> with your desired site name.

Create site with app installation

You can install apps during site creation:

docker compose -p frappe exec backend bench new-site <sitename> \
  --mariadb-user-host-login-scope='%' \
  --db-root-password <db-password> \
  --admin-password <admin-password> \
  --install-app erpnext

Note: Wait for the db service to start and configurator to exit before trying to create a new site. Usually this takes up to 10 seconds.

For more site operations, refer to site operations.

Understanding the MariaDB User Scope

The flag --mariadb-user-host-login-scope='172.%.%.%' allows database connections from any IP address within the 172.0.0.0/8 range. This includes all containers and virtual machines running on your machine.

Why is this necessary? Docker and Podman assign dynamic IP addresses to containers. If you set a fixed IP address instead, database connections will fail when the container restarts and receives a new IP. The wildcard pattern ensures connections always work, regardless of IP changes.

Security note: This scope is sufficient because only the backend container accesses the database. If you need external database access, adjust the scope accordingly, but be cautious with overly permissive settings.

Back: Build Setup →

Next: Setup Examples →