port binding of a public docker image service
bernatgene
PROOP

9 months ago

I've added a service via a public docker image; adminer. The service has a private url to communicate, but how do I set to communicate to the right port?

For reference, locally, I bind the 8080 port when I spin up the container, which is were adminer talks to. But on production, how can another one of my services communicate to ${{RAILWAY_PRIVATE_DOMAIN}}:8080 ? I can't find an option there.

Do I need manually create an image that does the expose inside the image itself?

Solved

4 Replies

bernatgene
PROOP

9 months ago

f4a24561-151c-4a6c-91b7-e9ac75a5a9c2


bernatgene
PROOP

9 months ago

Maybe all services running in the private network are accessible directly? so if I just do http://private_domain:8080 will work?


9 months ago

correct, as long as you listen on IPv6, since the private network is IPv6 only


9 months ago

!s


Status changed to Solved brody 10 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...