Railway•6mo ago

Urgent: more than 24h unable to deploy due to Docker Errors on railway build

No answer from Railway team on this issue so far. Projects fail to build on step 18 #18 ERROR: process "/bin/bash -ol pipefail -c yarn install --frozen-lockfile" did not complete successfully: exit code: 128 Project ID this time is ce1ecc45-867e-4ff6-abd1-26e97b8b345b I have tried deleting and recreating projects, deploying either from github or CLI, the error seems to be on Railway end. I am losing credibility because of this issue.

14 Replies

Percy•6mo ago

Project ID: ce1ecc45-867e-4ff6-abd1-26e97b8b345b

MantisInABox•6mo ago

Can you share the entire build log?

MaxB•6mo ago

Sure, here it goes

MaxB•6mo ago

railwaybuildlogce1ec...

MantisInABox•6mo ago

#18 0.967 [1/4] Resolving packages...

#18 1.044 [2/4] Fetching packages...

 

#18 1.202 error Command failed.

#18 1.202 Exit code: 128

#18 1.202 Command: git

#18 1.202 Arguments: ls-remote --tags --heads ssh://git@github.com/basecamp/idiomorph.git

#18 1.202 Directory: /app

#18 1.202 Output:

#18 1.202 "ssh" -oBatchMode=yes: 1: ssh: not found

#18 1.202 fatal: Could not read from remote repository.

#18 1.202

#18 1.202 Please make sure you have the correct access rights

#18 1.202 and the repository exists.

 

#18 1.202 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

 

#18 ERROR: process "/bin/bash -ol pipefail -c yarn install --frozen-lockfile" did not complete successfully: exit code: 128

#18 0.967 [1/4] Resolving packages...

#18 1.044 [2/4] Fetching packages...

 

#18 1.202 error Command failed.

#18 1.202 Exit code: 128

#18 1.202 Command: git

#18 1.202 Arguments: ls-remote --tags --heads ssh://git@github.com/basecamp/idiomorph.git

#18 1.202 Directory: /app

#18 1.202 Output:

#18 1.202 "ssh" -oBatchMode=yes: 1: ssh: not found

#18 1.202 fatal: Could not read from remote repository.

#18 1.202

#18 1.202 Please make sure you have the correct access rights

#18 1.202 and the repository exists.

 

#18 1.202 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

 

#18 ERROR: process "/bin/bash -ol pipefail -c yarn install --frozen-lockfile" did not complete successfully: exit code: 128

It looks like you have multiple issues... package-lock.json exists and you are using yarn, get rid of this file. You should only have yarn.lock, and it also looks like it is failing because of the basecamp/idiomorph repository.

#18 [stage-0 14/21] RUN --mount=type=cache,id=s/8417d485-2f14-43ec-8814-73c3d36bc1d1-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 yarn install --frozen-lockfile

 

#18 0.897 yarn install v1.22.21

 

#18 0.963 warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.

#18 0.967 [1/4] Resolving packages...

#18 1.044 [2/4] Fetching packages...

#18 [stage-0 14/21] RUN --mount=type=cache,id=s/8417d485-2f14-43ec-8814-73c3d36bc1d1-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 yarn install --frozen-lockfile

 

#18 0.897 yarn install v1.22.21

 

#18 0.963 warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.

#18 0.967 [1/4] Resolving packages...

#18 1.044 [2/4] Fetching packages...

This is not detremental, but it can potentially cause some issues

MaxB•6mo ago

I don't use basecamp on this project...

MantisInABox•6mo ago

Can you share your package.json file?

MaxB•6mo ago

Here

package.json

MaxB•6mo ago

Pushing without package-lock.json Package-lock is an inconvenience i never had to deal with my other projects, happens all the time because there are things that are Yarn-only and things that are npm-only Lines 103 from 115 of the deployment log caught my attention

1.202 Output:

1.202 "ssh" -oBatchMode=yes: 1: ssh: not found

1.202 fatal: Could not read from remote repository.

1.202

1.202 Please make sure you have the correct access rights

1.202 and the repository exists.

1.202 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

1.202 Output:

1.202 "ssh" -oBatchMode=yes: 1: ssh: not found

1.202 fatal: Could not read from remote repository.

1.202

1.202 Please make sure you have the correct access rights

1.202 and the repository exists.

1.202 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

MantisInABox•6mo ago

If a package you are using is a private repo, you will not be able to pull it, as you cannot import ssh keys in your project

MaxB•6mo ago

but I should be able to deploy via CLI , right ? I've aborted the github deploy and I am pushing the project via CLI ecfcdb6e-7f6c-43da-b0df-52065046e546 It failed the same way

MaxB•6mo ago

ecfcdb6e-7f6c-43da-b...

MaxB•6mo ago

c41434ca-3797-4684-ab51-f95f21037cda is a very simmilar project (that even has a package-lock.json) where I've made a deployment without any errors about 24h ago I have also deployed 299301f2-e17c-415e-b92a-b23584c8f4a0 24h ago with a very simmilar build , and it uses way more mixed yarn/npm packages But these two i've mentioned are projects that were previously deployed. My issue started on Dec 7th on all the new projects @Vin sorry, you there?

MantisInABox•6mo ago

#🛂｜readme rule 5, please don't tag people directly... I am trying to assist in between tasks at work

Gaming

Programming

Urgent: more than 24h unable to deploy due to Docker Errors on railway build