You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ran into an port issue when i ran docker compose -f compose.dev.yml because it was trying to stand up a db on 5435 but I was already using that port. Chris from Osmind had some of the same feedback when he was trying to stand us up locally - he had conflicts with an existing set up.
Would be nice to be able to continue to search for a port if it finds the first port is already allocated, a better user experience compared to the user having to go and update things. For me, I already had a DB that I was actively using on that port so it was annoying to have to update it to use a new port for the docker compose would work.
we can run an init script before any of the containers are created to check what ports are open and then dynamically update the following scripts with those ports. Would have to make sure that we also update the seed scripts with the right port number as well.
evisdrenova
changed the title
[NEOS-1095] update compose scripts to check for open ports
[NEOS-1095] update docker compose scripts to check for open ports
May 14, 2024
I hear you on the open ports thing, however I think this is way more complex than it's worth.
A much simpler solution is to just change our default ports to something else.
Many examples on the internet use these ports which is why it is a conflict.
ran into an port issue when i ran
docker compose -f compose.dev.yml
because it was trying to stand up a db on5435
but I was already using that port. Chris from Osmind had some of the same feedback when he was trying to stand us up locally - he had conflicts with an existing set up.Would be nice to be able to continue to search for a port if it finds the first port is already allocated, a better user experience compared to the user having to go and update things. For me, I already had a DB that I was actively using on that port so it was annoying to have to update it to use a new port for the docker compose would work.
we can run an init script before any of the containers are created to check what ports are open and then dynamically update the following scripts with those ports. Would have to make sure that we also update the seed scripts with the right port number as well.
From SyncLinear.com | NEOS-1095
The text was updated successfully, but these errors were encountered: