Redeploying a service fails
silviust7
HOBBYOP

2 months ago

Getting this error when redeploying a service it was deplyed 9 hours ago. Is it an issue on your end?

Project id: 3534901f-2f6f-4a72-979c-c6ec6d376f99

stage-0

RUN npm ci

1s

npm warn config production Use --omit=dev instead.

npm error code EUSAGE

npm error

npm error The npm ci command can only install with an existing package-lock.json or

npm error npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or

npm error later to generate a package-lock.json file, then try again.

npm error

npm error Clean install a project

npm error

npm error Usage:

npm error npm ci

npm error

npm error Options:

npm error [--install-strategy ] [--legacy-bundling]

npm error [--global-style] [--omit [--omit ...]]

npm error [--include [--include ...]]

npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]

npm error [--no-bin-links] [--no-fund] [--dry-run]

npm error [-w|--workspace [-w|--workspace ...]]

npm error [-ws|--workspaces] [--include-workspace-root] [--install-links]

npm error

npm error aliases: clean-install, ic, install-clean, isntall-clean

npm error

npm error Run "npm help ci" for more info

npm error A complete log of this run can be found in: /root/.npm/_logs/2026-03-19T16_04_33_625Z-debug-0.log

Build Failed: build daemon returned an error < failed to solve: process "/bin/bash -ol pipefail -c npm ci" did not complete successfully: exit code: 1 >

10 Replies

Make sure you commit your lockfile.


One way to do this is to run npm i on your local machine, then commit the generated lockfile to your repository.


Also, make sure you haven’t ignored the lockfile in your .gitignore.


silviust7
HOBBYOP

2 months ago

well i was able to deploy it 9 hours ago, don't understand why wouldn't it crash then but now


makorism
HOBBY

2 months ago

I'm getting the same issue, able to deploy a new change but trying to redeploy gives me

failed to read Dockerfile at /Dockerfile.wordpress


edgnkv
EMPLOYEE

2 months ago

Hey,

It looks like a bug.

I will take a look!


silviust7
HOBBYOP

2 months ago

found anything?


edgnkv
EMPLOYEE

2 months ago

It was a regression in the recent code change. I've disabled this change via a feature flag. So redeployment of new deployments should work now.


edgnkv
EMPLOYEE

2 months ago

sorry about the issue


silviust7
HOBBYOP

2 months ago

no problem, glad you caught it again, thanks


Welcome!

Sign in to your Railway account to join the conversation.

Loading...