Sign in

monday 8am and the postgres container won't bind to 443

Solvedcomposedockerports2 replies · 121 views · started
Reply

Accepted solution

by Clara SorensenJump to the reply

oof a natively installed service is a common culprit: local Postgres on 5432, Redis on 6379, Apache or IIS on 80. systemctl status postgresql or Get-Service on Windows will tell u, stop it or map teh container to another host port ("5433:5432").

  1. Lars T.
    @tensorhound-3oe

    help!! just tyring to start teh Postgres container with docker compose up on the staging VM and I get:

    docker ps shows nothing running... i rebooted Docker... still the same... i need this running for a demo in an hour and Im getting desperate.

    im not a Docker expert, i mostly copy compose files from teh team wiki and they usulaly just work... rebooting teh whole machine is my next step, but Id rather understand whats going on before i lose all my open windows.

    cry

    27
  2. Clara Sorensen
    @latetrace
    Accepted solution

    oof a natively installed service is a common culprit: local Postgres on 5432, Redis on 6379, Apache or IIS on 80. systemctl status postgresql or Get-Service on Windows will tell u, stop it or map teh container to another host port ("5433:5432").

    1 2 helpful
  3. Lars T.
    @tensorhound-3oe
    in reply to @latetrace

    @latetrace omggg stopped the forgotten native service and the Postgres container came right up on 443. demo saved with ten minutes to spare.

    0 2 helpful
Read next · Automation & DevOps
MY CRON SCRIPT WORKS BY HAND AND FAILS AT 3 AM WITH MODULENOTFOUNDERROR 🤔
Solved · 5 replies
Read

Reply to this topic

Sign in or create an account to reply.