Frappe/erpnext-worker ERROR

Can someone help me?

I’m trying to install ERPNext through docker and the image below contains the error

This is the sample credentials I provided on the .env file

Where did you place the env file? should be inside the installation/ directory and not outside of it.

yes I placed it in the installation directory


I also tried it manually

Thank you for your reply, I’ll give this a try

Hi revant_one, I managed to successfully install ERPNext through docker with your previous suggestion. However, I’m facing a We will be back soon problem. How can I fix this?
Thank you

I’ve encountered this error when I execute the command below
–project-name erpfirst
-f installation/docker-compose-common.yml
-f installation/docker-compose-erpnext.yml
-f installation/docker-compose-networks.yml
–project-directory installation up -d

what are the container logs? for erpnext-python, erpnext-nginx containers

If you’re trying out locally skip the network docker-compose

Hi, I am trying to install ERPNext through docker on AWS EC2 Ubuntu 18.04

what are the container logs?

docker logs <container_name>

to know container names use command:

docker ps

Thank you for your prompt reply, I’ll start the server again and try this

Also make sure you have added a new site. Refer:


Supposed that I managed to successfully installed and configured ERPNext through docker.
How are we going to create our custom changes then?
Should we create new images for specifically for our code changes?

Yes you need to build image. Here are instructions

I’ve not yet built custom app images.

Report issues if you face any problem

Noted on this, thank you

Is it okay to install Multiple ERPNext instances on a single server?
For instance, there are three users on the server
3 instances are installed and configured through easy install script
apply some code changes in each instance like ports
Is this applicable? What will happen if I execute bench restart while the other ERPNext instance is running

You can install as many instances as the server can support

In case of production deployments ports are not published by docker, only the docker-compose-letsencrypt-nginx-proxy-companion publishes the required ports, i.e. 443 and 80.

This means you can repeat the installation, just change the <project-name> and number of docker-compose projects will be running.

There is no bench.
There is no supervisor, docker does the job of supervisor. Docker keep the containers running and manage replicas of containers.

you can manage these projects independently without restarting server

Read about docker stack, docker-compose and it can do a lot of things with containers. Checkout closed issues and PRs. Community is using it in different ways. People are using traefik instead of docker-compose-letsencrypt-nginx-proxy-companion.