Railway still using dockerfile even though RAILPACK is specified in railway.json
colemandunn
PROOP

8 months ago

here is my railway.json

{
  "$schema": "https://railway.com/railway.schema.json",
  "build": {
    "builder": "RAILPACK"
  }
}

Yet I get the following message in the posted image when I try to deploy.

Trying to get around this problem seen in these messages by using railpack: https://discord.com/channels/713503345364697088/1271544895861035068/1360290382306607224

Constraints: we have a dockerfile at the root (do not want (cannot) change this)

Solved

7 Replies

colemandunn
PROOP

8 months ago

N/A

adam
MODERATOR

8 months ago

If a dockerfile is detected, it will bypass railpack and be used. If you don’t want it to be used, rename it. Only dockerfiles named “Dockerfile” are detected

adam
MODERATOR

8 months ago

if this is a feature request, please post it in #🤗｜feedback

colemandunn
PROOP

8 months ago

Ok thanks, I may do that. At first I viewed this as a bug based on the docs mentioning that railway.json takes priority (not specifically over automatic docker detection tbf)

colemandunn
PROOP

8 months ago

I think the more preferred feature if I were to make one would be to have RAILWAY_SERVICE_ID available as an ENV during builds like mentioned in the linked thread. Not sure if that is not possible or has been suggested/shut down already.

adam
MODERATOR

8 months ago

Valid feedback, maybe open a #🤗｜feedback post? The docs change can be actioned immediately, but the rest may take some time

adam
MODERATOR

8 months ago

!s

Status changed to Solved adam • 8 months ago

Loading...