-
Notifications
You must be signed in to change notification settings - Fork 341
Description
I am following the deployment instructions in the README.md for a self-hosted setup. The guide instructs users to install Nginx via apt on the host machine, and then subsequently run setup.sh to deploy the Docker containers.
However, because the huly_v7-nginx-1 container is configured to bind to host port 80:80, it fails to start because the system-level Nginx (installed in the previous step) is already occupying that port.
On a fresh Ubuntu server, follow the README instructions.
Run sudo apt update and sudo apt install nginx.
Clone the repository and run ./setup.sh.
Enter the host address and select No for SSL (HTTP only).
Agree to run docker compose up -d.
The deployment should start successfully, or the documentation should clarify how to configure the system Nginx to proxy traffic to the Docker container without causing a port binding conflict.
Actual Behavior: The Docker containers fail to start. The system Nginx holds Port 80, preventing the Docker ingress from binding.
[+] Running 14/15
...
✔ Container huly_v7-elastic-1 Started 1.7s
⠹ Container huly_v7-nginx-1 Starting 2.3s
...
Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint huly_v7-nginx-1 (...): failed to bind host port 0.0.0.0:80/tcp: address already in use
Environment:
OS: Ubuntu 24.04
Deployment: Docker Compose via setup.sh
SSL Selection: No (HTTP only)