Open Krieke opened 1 year ago
Hello @Krieke,
I have built the following SUT environment to simulate your case as closely as possible:
I have not been able to replicate "port 80 is already in use" with the conditions above.
I would suggest as an initial approach to comment out lines 7 (- 80:80) and 96 (- "81:80") from the docker-compose.yml
file . The pulled nginx
image does use port 80 as well and may be causing a problem on your end.
Let me know if you keep experiencing the same issue.
@aitorcelaya I noticed the port issue both on my Linux and Mac OS environment. Of course I already modified the docker-compose.yml file so that this issue is fixed on my local setup.
My remark about adapting the docker-compose.yml file in such away that it is clear which ports are being mapped remains, but is not mandatory of course. It is just a proposal for improvements. I am not blocked :-)
Describe the bug main:latest docker-compose.yml multiple services try to bind on local IP port 80 also it would be better that one can view directly within the docker-compose file which IP ports are used by the services. Using expose for inter service communication or ports which is the same then the latter, with the difference that the port is also exposed outside the docker environment.
To Reproduce Steps to reproduce the behavior:
docker-compose
upExpected behavior All services are bootstrapped without issue
SUT environment