Port Binding Issue During Frappe Builder Installation on Docker

When installing Frappe Builder using the Easy-Install script on Docker, an error occurs because port 80 is already in use by another service (e.g., CloudPanel). The script attempts to bind to port 80, but it fails as this port is already occupied by Nginx. This prevents the installation from continuing. The issue is that port 80 is occupied, and the installation cannot be redirected to another port because the service continuously uses port 80.

Hi,

Note the port assignment @revant_one uses in this example:

https://discuss.frappe.io/t/i-have-a-problem-when-use-frappe-with-docker-and-custom-app/141881/4?u=smino

1 Like

failed to bind port 0.0.0.0:80/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use
Docker Compose failed, please check the container logs

This is how the error is displayed as soon as I insert the port information. My problem is that I previously installed CloudPanel to make it easier to add my websites later and set up the environment.
However, I thought that if I create a new directory and install the Frappe builder there, and assign a subdomain to it, it would work without problems. But when I run easy-install.py and then the python3 command, I constantly get the error that port 80 is occupied, which is completely fine. Then I changed the docker-compose.yml and adjusted the ports, but as soon as I enter the python3 command, the ports are reset.
In other words, installing the Frappe builder using the easy install script doesn’t seem to work with my method, and I wanted to ask in this forum if anyone had an idea about this