Builds are failing suddenly
hikieadmin
PROOP

a month ago

My builds are failing suddenly and im seeing this logs in building

UndefinedVar: Usage of undefined variable '$NIXPACKS_PATH' (line 18)(https://docs.docker.com/go/dockerfile/rule/undefined-var/) details: Variables should be defined before their use

before i dont have these logs, suddenly they appeared then it says nest not found, its impossible

Solved$20 Bounty

3 Replies

Railway
BOT

a month 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 28 days ago


Status changed to Solved hikieadmin 28 days ago


edgnkv
EMPLOYEE

a month ago

Hello,

The issue is not undefined variable (this is a warning), but related to a new version of Nixpacks that is used by Metal builders (we are in the process of migrating everyone to new builders).

Nixpacks is overall deprecated and we strongly recommend to migrate to Railpack.


Status changed to Awaiting User Response Railway 28 days ago


edgnkv

Hello, The issue is not undefined variable (this is a warning), but related to a new version of Nixpacks that is used by Metal builders (we are in the process of migrating everyone to new builders). Nixpacks is overall deprecated and we strongly recommend to migrate to Railpack.

Anonymous
PRO

a month ago

They DONT F* work, all of my builds are hanging, why are you guys enabling them randomly, is it too hard to set a deadline for migration and stay silent meanwhile?


Status changed to Awaiting Railway Response Railway 28 days ago


They DONT F\* work, all of my builds are hanging, why are you guys enabling them randomly, is it too hard to set a deadline for migration and stay silent meanwhile?

edgnkv
EMPLOYEE

a month ago

The goal is to be compatible with old builders, so most of the time users should have no need to do anything. We have been testing metal builders for a while and now we want to move forward.

The issue that you faced is related to usage of watchPatterns. The fix is already in the merged queue and will be rolled to prod today.


Status changed to Awaiting User Response Railway 28 days ago


Railway
BOT

21 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...