How to configure Docker image is listening on ipv6?
jenxltd
HOBBYOP

3 months ago

I'm trying to run a simple libsql server with the following image: ghcr.io/tursodatabase/libsql-server:latest

It seems to run the image, but I'm not sure how to configure the docker networking to listen to requests on ipv6 in route them to an internal 0.0.0.0:8080 address through the Railway UI.

Basically I just want to run the Docker image with the following options:

-p[::]:8080:8080

Is this possible?

Solved$10 Bounty

8 Replies

Railway
BOT

3 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


fra
HOBBY

3 months ago

I suppose you can expose the port you need in the dockerfile and then select the same port in the network tab

Attachments


fra

I suppose you can expose the port you need in the dockerfile and then select the same port in the network tab

jenxltd
HOBBYOP

3 months ago

How do I edit the dockerfile? Can I edit the docker file for a service?

Also I don't want this db to be public, I only want it to be used internally so I don't really want to expose it tbh!


fra
HOBBY

3 months ago

probably I misunderstood, looking at the dockerfile of this image it already exposes the ports 8080 and 5001.

If you need a public url you should be able to create a random url and map it to the port you need (8080) using the railway UI (Network->Public Networking).

If you want to connect to the db from an internal service in the internal network you should be able to just use the internal host (you can see the host here: Network->Provate network) and use the port 8080 or 5001


mardonedias
PRO

3 months ago

I believe that to gain internal access, you only need to enter the internal railway address followed by the port:

e.g., nginx-prod.railway.internal:8080

Attachments


mardonedias

I believe that to gain internal access, you only need to enter the internal railway address followed by the port:e.g., nginx-prod.railway.internal:8080

jenxltd
HOBBYOP

3 months ago

Ah yeah ok, so when I put the port that does work! Thank you, I'm not sure why it wasn't requesting the port before but oh well!


fra
HOBBY

3 months ago

can I you resolve the question so one of us get the bounty?


mardonedias

I believe that to gain internal access, you only need to enter the internal railway address followed by the port:e.g., nginx-prod.railway.internal:8080

pbronez
HOBBY

3 months ago

Thanks for this - I was missing the port. Threw me off because the public networking includes port mapping.


Status changed to Solved uxuz 3 months ago


Loading...