Dockerfile'd image runs perfectly locally but instantly eats up all available ram and kills itself
flatypus
PROOP

a year ago

Was trying to run a dockerfile to run the livekit agents workflow. The code provides a cli app that takes in either 'dev' or 'start'; both dev and start work perfectly when run locally, but when the dockerfile is given to a railway container, it can only run dev fine; every attempt I've tried to run start has caused it to crash out

3 Replies

flatypus
PROOP

a year ago

3f0bd135-48b7-4e16-ad25-c1121e985d0f


a year ago

is the application cgroup aware?


a year ago

if not, when ran on Railway it's going to see 400 something gigabytes of memory, and some applications just use whatever is available


Welcome!

Sign in to your Railway account to join the conversation.

Loading...