Communication between services inside the same docker image
My services are not able to communicate with each other. Is what I am trying to do wrong?
25 Replies
Project ID:
6ef7539d-c186-4609-a904-178fd8fa7fa06ef7539d-c186-4609-a904-178fd8fa7fa0
does
localhost not work in railway?is the api running within the same container?
yeah
try
127.0.0.1it works this way locally and on fly so im wondering why it does not here.
not sure, but please try
yeah it is deploying. taking a lot of time for whatever reason
Definitely should not be taking this much time
its just a docker image
Railway is aware of the slow downs and is continually improving it
alright. its deployed. its still not working
is there a way to ssh into the running service?
there is not, please provide specific errors
Solution
how do you know that the api is running on
0.0.0.0 and 8000Does railway inject a variable called
PORT?yes
how do i remove it?
you can't, im not sure why you want to?
I have a custom reverse proxy setup inside the docker image with tightly coupled services
you can change it by setting your own PORT variable
alright trying that
working now.
removed this as well
id recommend you stay with 127.0.0.1, one less dns lookup
hmm. is this not cached at some level?
should i do it on the reverse proxy as well?
no?
yes
okay. thank you very much for your help. this can be closed.