Railway•12mo ago

Deploys suddenly seem to ignore railway.json to use dockerfile

Project ID: 3705332d-0483-45f4-af73-a7e805fc639f Hi. Did something change between Friday and today that would cause railway to build a nixpack instead of using our Dockerfile? I am trying to troubleshoot an issue where our deploys started to build nixpack instead of using our Dockerfile. A few weeks ago, we configured our railway.json build to use dockerfile and it worked until today. Our last successful deploy was Friday. We have not changed the railway.json or Dockerfile since Nov 3. Here is our railway.json

{
  "$schema": "https://railway.app/railway.schema.json",
  "build": {
    "builder": "DOCKERFILE"
  },
  "deploy": {
    "restartPolicyType": "ON_FAILURE",
    "restartPolicyMaxRetries": 10
  }
}

{
  "$schema": "https://railway.app/railway.schema.json",
  "build": {
    "builder": "DOCKERFILE"
  },
  "deploy": {
    "restartPolicyType": "ON_FAILURE",
    "restartPolicyMaxRetries": 10
  }
}

Here is deploy log indicating nixpack build failure

[Region: us-west1]
==============
Using Nixpacks
==============
context: 3b47e39ba0d248de10ac14cc8d70e062
Nixpacks build failed
 
 
╔══════════════════════════════ Nixpacks v1.19.0 ══════════════════════════════╗
║ setup      │ python310, postgresql, gcc                                      ║
║──────────────────────────────────────────────────────────────────────────────║
║ install    │ python -m venv --copies /opt/venv && . /opt/venv/bin/activate   ║
║            │ && pip install poetry==$NIXPACKS_POETRY_VERSION && poetry       ║
║            │ install --no-dev --no-interaction --no-ansi                     ║
║──────────────────────────────────────────────────────────────────────────────║
║ start      │                                                                 ║
╚══════════════════════════════════════════════════════════════════════════════╝
 
Error: No start command could be found

[Region: us-west1]
==============
Using Nixpacks
==============
context: 3b47e39ba0d248de10ac14cc8d70e062
Nixpacks build failed
 
 
╔══════════════════════════════ Nixpacks v1.19.0 ══════════════════════════════╗
║ setup      │ python310, postgresql, gcc                                      ║
║──────────────────────────────────────────────────────────────────────────────║
║ install    │ python -m venv --copies /opt/venv && . /opt/venv/bin/activate   ║
║            │ && pip install poetry==$NIXPACKS_POETRY_VERSION && poetry       ║
║            │ install --no-dev --no-interaction --no-ansi                     ║
║──────────────────────────────────────────────────────────────────────────────║
║ start      │                                                                 ║
╚══════════════════════════════════════════════════════════════════════════════╝
 
Error: No start command could be found

4 Replies

Percy•12mo ago

Project ID: N/A

Brody•12mo ago

use this to redeploy your service https://bookmarklets.up.railway.app/service-redeploy/ let me know if that works, otherwise i will tag in the team

JacobOP•12mo ago

Thanks. I shared your help with the team. They did not try the service-redeploy. They started a new build since they needed to update packages anyway. That time it used the Dockerfile as expected. Is there anyway on our end to identify why it tried building nixpack instead of docker?

Brody•12mo ago

its a bug with railway

Gaming

Programming

Deploys suddenly seem to ignore railway.json to use dockerfile