MaxB
MaxB
RRailway
Created by MaxB on 12/8/2023 in #✋|help
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.
25 replies
RRailway
Created by MaxB on 12/7/2023 in #✋|help
Multiple Deploy Failures - Docker Error 128
Multiple deploy failures, the error always happens on step #18 (yarn installation of ruby project), the service ID are as follows: 4c0d7cfe-345f-4c31-8256-102d90e6a0c0 8ef1f0aa-7846-4b40-97e5-e40d5a8c81f6
3 replies
RRailway
Created by MaxB on 12/7/2023 in #✋|help
Docker Build Failed, #18 step - Yarn installation
Project ID - 5b62b527-347c-4928-bc7e-24990f625775 Since yesterday I am unable to deploy from either GitHub or CLI , reason being the following error shows up: #18 ERROR: process "/bin/bash -ol pipefail -c yarn install --frozen-lockfile" did not complete successfully: exit code: 128 ERROR: failed to solve: process "/bin/bash -ol pipefail -c yarn install --frozen-lockfile" did not complete successfully: exit code: 128 Full error log: #18 [stage-0 14/21] RUN --mount=type=cache,id=s/7e19c86b-b55e-41f7-a62d-5a0290067bed-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 yarn install --frozen-lockfile
5 replies
RRailway
Created by MaxB on 10/26/2023 in #✋|help
Railway Up from CLI not Uploading
I am trying to upload from CLI and upload is failing. Double checked login credentials and CLI version. It Indexes and Compresses but fails on the Upload Stage. Dashboard shows "Initializing" up to the point of probably a timeout. Service ID is ef432bde-9674-4182-99f4-1e646957acb5 Error message is: Cannot create code snapshot right now, please review your last commit or try again If this error persists, please reach out to Railway team
2 replies