3 months ago
but no shell is provided. And if I do interrupt it (ctrl + c)., I'll get the following error
railway ssh --environment=6f940eff-1500-403a-8811-0a594df0a611 --service=010423f7-b406-4cd9-83f1-16b9d8b9c4d2
⠴ Connection attempt 1 failed: IO error: tls handshake eof. Retrying in 5 seconds...
⠴ Connection attempt 1 failed: IO error: tls handshake eof. Retrying in 5 seconds...
✓ Connected to interactive shell Error: container create failed (no logs from conmon): conmon bytes "": readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
I do get different error now -
Is there any official delayed railway support if not immediately?
> ✓ Connected to interactive shell
> Error: crun: read pipe failed: OCI runtime error
2 Replies
3 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 3 months ago
3 months ago
The conmon/crun errors happen because Railway's SSH tries to spawn a shell that doesn't exist in minimal images.
The issue is your base image lacks a proper shell. Switch from a slim/distroless/alpine image to a full one in your Dockerfile: FROM node:20
(or python:3.12, ubuntu:24.04, etc. whatever your stack is)
Then redeploy from the railway.
dostogircse171
The `conmon`/`crun` errors happen because Railway's SSH tries to spawn a shell that doesn't exist in minimal images. The issue is your base image lacks a proper shell. Switch from a slim/distroless/alpine image to a full one in your Dockerfile: `FROM node:20` (or `python:3.12`, `ubuntu:24.04`, etc. whatever your stack is) Then redeploy from the railway.
3 months ago
I'm using full image which is node:22-bookworm. Not a slim/ alpine image. I do no think it is because of the image, because another service with buildEnvironment null is working fine, while this with buildEnvironment v3 is not working.