Why i cant solve the problem

[nowindbird]

🔑 Generating MinIO keys...
✅ MinIO keys generated successfully
🔑 Generating Supabase keys...
✅ Supabase keys generated successfully
🔧 Starting infrastructure services...
[+] Running 38/38
✔ nexent-minio Pulled 128.2s
✔ nexent-elasticsearch Pulled 491.0s
✔ nexent-postgresql Pulled 683.7s
✔ redis Pulled 49.2s

[+] Running 1/5
✔ Network nexent_nexent Created 0.1s
⠇ Container nexent-minio Starting 0.8s
⠇ Container nexent-redis Starting 0.8s
⠇ Container nexent-postgresql Starting 0.8s
⠇ Container nexent-elasticsearch Starting 0.8s
Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint nexent-postgresql (14a5493be3d1a7841e6fcd8327ec928b23d7474ac1ac30a2d68dc242e2acbb5c): failed to bind host port for 0.0.0.0:5434:172.18.0.2:5432/tcp: address already in use
❌ ERROR Failed to start infrastructure services
root@LAPTOP-Q8VTGOPA:~/nexent/docker#

[Phinease]

It seems like your docker driver is misbehaving. Maybe you should update your docker. Can I know your docker and docker compose version?

[nowindbird]

“it just take the port, i restart my computer and solve it. its another question that the sql version is higher so that the healthy service is not able to handshake successfully.”

[Phinease]

“it just take the port, i restart my computer and solve it. its another question that the sql version is higher so that the healthy service is not able to handshake successfully.”

Do you mean the host server's sql version? Will it influence the health check inside docker? If so, can I see the screenshot maybe? Thank you.

[nowindbird]

[Phinease]

This seems a little bit weird. I suggest you remove all files in $ROOT_DIR then try to redeploy. This may due to some file path permission. If not working, you are welcome to connect me by wechat.