Run dockerfile exposing 8000 port?

[lime carbon]

i am trying to run https://github.com/chroma-core/chroma dockerfile

it works on my machine but i can't expose the port 8000 on railway. the dockerfile exposes the 8000 port. heres how it runs on my machine:

docker build
docker run -p 8000:8000

[tight wagon]

Project ID: 186328e3-739e-42c7-9076-98f6f6efeb5d

[lime carbon]

186328e3-739e-42c7-9076-98f6f6efeb5d

[glacial cipher]

you would just set PORT = 8000 in your service variables

[lime carbon]

if i run docker in the build/run stage on railway itself it says docker isn't a valid command

like this?

[glacial cipher]

but this app wont work on railway if

1. it doesn't communicate over http/ws
   or
2. needs persistent storage

[lime carbon]

it does communicate over https. i can actually show you logs that show its running on 0.0.0.0:8000

no persistent storage -- i will change that later, just trying to get it to work

rolling back now -- i can share the deployment in a sec

deployment: bd7b3224-41d2-4475-8e7b-3b25ecada779

if thats at all helpful

[glacial cipher]

i cant do a single thing with that

the bot asks you to provide it incase the team needs to get involved, and in your case, they dont

[lime carbon]

here is what i see

https://chromadb.up.railway.app is the domain
8000 is the port it should be on but for some reason railway isn't opening that up

[glacial cipher]

you can only access your service over port 443, setting PORT = 8000 just tells railway to forward traffic between 8000 internally and 443 externally

accessing your app from https://chromadb.up.railway.app/ works

using the https schema without a specified port implies the use of port 443

[lime carbon]

is there no support for http?

[glacial cipher]

thats correct, secure by default and only secure

[lime carbon]

alright...ssl is a pain but found a hidden variable that enables it in the library i am trying to use. great work

[lusty mica]

@lime carbon were you able to get this to work? I tried setting ssl=True but still timeout 😦

[glacial cipher]

their app worked just fine
#1100601530660429904 message

[lusty mica]

I see, unfortunately still timing out though when trying to connect from Chroma client. Wondering if I need to set anything else in the server config besides ssl=True, maybe need to change hostname and port?

    chroma_server_host: Optional[str] = None
    chroma_server_headers: Optional[Dict[str, str]] = None
    chroma_server_http_port: Optional[str] = None
    chroma_server_ssl_enabled: Optional[bool] = False
    chroma_server_grpc_port: Optional[str] = None
    chroma_server_cors_allow_origins: List[str] = []  # eg ["http://localhost:3000"]

[glacial cipher]

wanna open your own thread please?

[lusty mica]

yeah will do, just thought it would make sense to continue the conversation here because it is the same topic

[glacial cipher]

i can see your logic but that just sends a bunch of notifications to the op