Crashed while trying to connect with sequelize
pablofriascampos
TRIALOP

a year ago

Build Logs: https://railway.app/project/3bf23a2b-38aa-4ee7-a455-0b9e5bdb8054/service/19c69aa8-e3e7-42a5-9e67-ecbb78b2e293?id=8f7112a0-0676-4463-abb7-12c5244cdc76&

[Region: us-west1]

Using Nixpacks

context: 45524e0f4c4b96992e4e2dc52a1c45dc

╔══════════════════════════════ Nixpacks v1.29.0 ══════════════════════════════╗
║ setup │ nodejs18, yarn-1x ║
║──────────────────────────────────────────────────────────────────────────────║
║ install │ yarn install --frozen-lockfile ║
║──────────────────────────────────────────────────────────────────────────────║
║ start │ docker-entrypoint.sh mysqld --innodb-use-native-aio=0 ║
║ │ --disable-log-bin --performance_schema=0 ║
╚══════════════════════════════════════════════════════════════════════════════╝

0 building with "builder-b-Bf" instance using docker-container driver

1 [internal] load build definition from Dockerfile

1 transferring dockerfile: 2.44kB done

1 DONE 0.0s

2 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1727136237

2 DONE 0.1s

3 [ 1/12] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1727136237@sha256:72cd12021740b1c4100a5c53c3b22974dacb86e4b0a35fcdd12605339de25b86

3 resolve ghcr.io/railwayapp/nixpacks:ubuntu-1727136237@sha256:72cd12021740b1c4100a5c53c3b22974dacb86e4b0a35fcdd12605339de25b86 done

3 DONE 0.0s

4 [ 2/12] WORKDIR /app/

4 CACHED

5 [internal] load .dockerignore

5 transferring context: 2B done

5 DONE 0.0s

6 [internal] load build context

6 transferring context: 67.39kB done

6 DONE 0.0s

7 [stage-0 7/8] RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile

7 CACHED

8 [stage-0 5/8] COPY . /app/.

8 CACHED

9 [stage-0 6/8] RUN --mount=type=cache,id=s/19c69aa8-e3e7-42a5-9e67-ecbb78b2e293-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 yarn install --frozen-lockfile

9 CACHED

10 [stage-0 3/8] COPY .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix

10 CACHED

11 [stage-0 4/8] RUN nix-env -if .nixpacks/nixpkgs-e05605ec414618eab4a7a6aea8b38f6fbbcc8f08.nix && nix-collect-garbage -d

11 CACHED

12 [stage-0 8/8] COPY . /app

12 CACHED

13 exporting to image

13 exporting layers 0.0s done

13 exporting manifest sha256:ffc2393db3a517bacbfb63368a4c872d75b2f2a392cc7f2ac0a12e9cd6b76762 done

13 exporting config sha256:546bd66bdd41caf8e8bd44014418403262a84aaa14d6b3e36a1632ccd56697ae done

13 exporting attestation manifest sha256:8e60730fcaedd3af0cf66dfe61bb13b5ab3f48ef3bec4197c115491cd3bb59d3 done

13 exporting manifest list sha256:58e356c1759c83eb46f82b149019e991a47d6b5d6d392ae462e36b2534770efb done

13 …

14 [auth] sharing credentials for us-west1.registry.rlwy.net

14 DONE 0.0s

13 exporting to image

13 pushing layers

13 pushing layers 1.5s done

13 pushing manifest for us-west1.registry.rlwy.net/19c69aa8-e3e7-42a5-9e67-ecbb78b2e293:8f7112a0-0676-4463-abb7-12c5244cdc76@sha256:58e356c1759c83eb46f82b149019e991a47d6b5d6d392ae462e36b2534770efb

13 pushing manifest for us-west1.registry.rlwy.net/19c69aa8-e3e7-42a5-9e67-ecbb78b2e293:8f7112a0-0676-4463-abb7-12c5244cdc76@sha256:58e356c1759c83eb46f82b149019e991a47d6b5d6d392ae462e36b2534770efb 1.0s done

13 DONE 2.6s

=== Successfully Built! ===

Run:
docker run -it us-west1.registry.rlwy.net/19c69aa8-e3e7-42a5-9e67-ecbb78b2e293:8f7112a0-0676-4463-abb7-12c5244cdc76

Build time: 3.12 seconds
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/da9e4fb2-9841-496c-82a2-1129830f67ca/volltwb6ix10a1n2h3q container event container died /bin/bash: line 1: docker-entrypoint.sh: command not found Deploy complete Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/da9e4fb2-9841-496c-82a2-1129830f67ca/volltwb6ix10a1n2h3q
Deploy crashed

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.

1 Replies

a year ago

You have ran railway up while linked to your database service, instead you need to railway up into a new service.

I've gone ahead and reverted to an older database deployment to fix that mistake for you.


Loading...