#Disk related error in rust app

40 messages · Page 1 of 1 (latest)

bright pilotBOT
#

Project ID: c455cbf9-7425-4a74-8c1d-17d41c5d793b

vivid wolf
#

There are zero limitations on the filesystem. Maybe the deployment is missing a system library and therefore is unable to untar the file?

tight basin
#

The same containers work just fine in Google Cloud run but don't in railway. Was hoping to understand what's missing on the railway side as it still seems buggy at times (volumes not allowed in certain locations, ui kicks you out or all options for creating new projects not available, etc). Are these documented anywhere or you just find out when using it?

vivid wolf
#

volumes not allowed in certain locations
yeah railway prevents you from mounting to system paths

ui kicks you out or all options for creating new projects not available
never seen this before, mind sharing some screenshots / screen recordings?

i have done "untaring" on railway both in code and with the tar cli, no issues, unfortunaly it works elsewhere does not rule out code issues.

tight basin
vivid wolf
#

may i ask why im seeing mention of .py files?

#

Is it the railway architecture?
nope

are you with railway?
nope

tight basin
#

oh, was hoping they could take a look at the projectid

#

it's rust, the error comes from that section

vivid wolf
#

what are the .py files for, is this rust or python?

lost socket
#

can i see your rust code for where this is erroring

#

oh wait, you are using a python wrapped library

#

that is an issue with the way their bindings work

tight basin
#

you looking at the project?

vivid wolf
#

neither of us work for railway

tight basin
#

lol, do the railway folks ever stop by?
why python are you looking at?

vivid wolf
#

they do, if this was a platform issue

tight basin
#

that's the question, I guess

vivid wolf
#

haha the answer being this isnt a platform issue

tight basin
#

how would you know if you haven't seen the project?

vivid wolf
#

as mentioned, i have untared files on railway in the past without issues

tight basin
#

respectfully, that doesn't prove this case is the same as those, people thought it was python

lost socket
#

this is not an issue with railway

#

this is an issue with the library you are using

#

are you using a dockerfile? maybe try a different runtime image

vivid wolf
#

agree with milo

tight basin
#

railway is great but right now is only suitable for dev loads or hobby projects, but they're getting there. I mean they didn't even have volumes before. Which is why I gave it another try

#

I think it could be either way, just can't be certain without having all the info though

lost socket
#

are you using nixpacks?

#

or a dockerfile

vivid wolf
#

railway runs a whole lot of business class users and helps them scale, that take is simply incorrect

tight basin
#

a docker image

lost socket
#

okay, what is the runtime image?

tight basin
#

it's not public, it's an EE version

lost socket
#

is it based on distroless? alpine? ubuntu?

#

the library might not work on that

tight basin
#

it works on cloud run, running prod there, was just trying to test out railway

#

ARG DEBIAN_IMAGE=debian:bookworm-slim
ARG RUST_IMAGE=rust:1.76-slim-bookworm
ARG PYTHON_IMAGE=python:3.11.8-slim-bookworm

FROM ${DEBIAN_IMAGE} as nsjail

#

do you guys know if the limitations are listed somewhere?

  • unallowed locations for volumes
  • no volumes for replicas
  • architectures supported
    etc
vivid wolf