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
When setting up a local polis deployment, any modification to the API_SERVER_PORT in .env seems ignored: the server still tries to bind to port 5000.
I observed this when running on a mac machine where port 5000 is already occupied by Airplay Receiver: setting API_SERVER_PORT to 52000 didn't work, the server still kept complaining that port 5000 was already used and it couldn't bind to it. In the end I gave up and stopped Airplay Receiver, which allowed me to free up port 5000 and get going with my main task, but documenting it here as we might eventually want to fix that.
I tried a few things to no avail, including:
Modifying the server service in docker-compose.dev.yml by adding:
Citing @colinmegill today: yup, that's expected at the moment, with the port number being peppered in a few different places in the code. There are plans to fix that, but towards end of 2025.
When setting up a local polis deployment, any modification to the
API_SERVER_PORT
in.env
seems ignored: the server still tries to bind to port5000
.I observed this when running on a mac machine where port
5000
is already occupied by Airplay Receiver: settingAPI_SERVER_PORT
to 52000 didn't work, the server still kept complaining that port5000
was already used and it couldn't bind to it. In the end I gave up and stopped Airplay Receiver, which allowed me to free up port 5000 and get going with my main task, but documenting it here as we might eventually want to fix that.I tried a few things to no avail, including:
server
service indocker-compose.dev.yml
by adding:polis/server/Dockerfile
Line 34 in 2542ce1
EXPOSE ${API_SERVER_PORT}
The text was updated successfully, but these errors were encountered: