bug: Server is marked as Ready even if the 80 port is already assign and haproxy has failed to start

[hagatopaxi]

Describe the bug

When the haproxy service is started, if there is another web server running on the server (and the port 80 and 443 already in use), haproxy will fail.

starting container failed: container af6a1c10bc4fb57c351fe4187e0ba59bc33ae1dae36ff06cdc843656c9b9eccc: endpoint join on GW Network failed: driver failed programming external connectivity on endpoint gateway_f9b87e6632b3 (b91f5465870c478fc2046d1fae0653e1af91ed56464b95d4c58fd78d6d950234): 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

[tanmoysrt]

@hagatopaxi
Currently, we just run the docker service for haproxy/udpproxy, and marked it as Ready.
Usually, it's recommended to install swiftwave on a new server. That's why this issues appears so less.

In new version, it will show realtime healthcheck infos of all the proxy. That should solve this issue as well.

[HWiese1980]

Ah, this is the bug I've been dealing with for the past couple hours. Yeah. Good to know this is already a known issue.