How to fix my problem
kinzart
TRIALOP

a year ago

[Region: us-west1]

==============

Using Nixpacks

==============

context: 095bd3aeabe30acca706c348d99bbb31

╔══════════════════════════════ Nixpacks v1.31.0 ══════════════════════════════╗

║ setup │ nodejs18, npm-9x, libnss3, libatk1.0-0, libatk-bridge2.0-0, ║

║ │ libcups2, libgbm1, libasound2, libpangocairo-1.0-0, libxss1, ║

║ │ libgtk-3-0, libxshmfence1, libglu1 ║

║──────────────────────────────────────────────────────────────────────────────║

║ install │ npm ci ║

║──────────────────────────────────────────────────────────────────────────────║

║ start │ npm run start ║

╚══════════════════════════════════════════════════════════════════════════════╝

[internal] load build definition from Dockerfile

[internal] load build definition from Dockerfile ✔ 0ms

[internal] load build definition from Dockerfile

[internal] load build definition from Dockerfile ✔ 15ms

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

[internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1736208272 ✔ 112ms

[internal] load .dockerignore

[internal] load .dockerignore ✔ 0ms

[internal] load .dockerignore

[internal] load .dockerignore ✔ 16ms

[stage-0 9/9] COPY . /app

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

[internal] load build context ✔ 0ms

[internal] load build context

[internal] load build context ✔ 859ms

[stage-0 3/9] COPY .nixpacks/nixpkgs-5624e1334b26ddc18da37e132b6fa8e93b481468.nix .nixpacks/nixpkgs-5624e1334b26ddc18da37e132b6fa8e93b481468.nix ✔ 0ms – CACHED

[stage-0 4/9] RUN nix-env -if .nixpacks/nixpkgs-5624e1334b26ddc18da37e132b6fa8e93b481468.nix && nix-collect-garbage -d ✔ 0ms – CACHED

[stage-0 5/9] RUN sudo apt-get update && sudo apt-get install -y --no-install-recommends libnss3 libatk1.0-0 libatk-bridge2.0-0 libcups2 libgbm1 libasound2 libpangocairo-1.0-0 libxss1 libgtk-3-0 libxshmfence1 libglu1 ✔ 0ms – CACHED

[stage-0 6/9] COPY . /app/.

[stage-0 6/9] COPY . /app/. ✔ 266ms

[stage-0 7/9] RUN --mount=type=cache,id=s/0e44f111-8d88-44bf-958d-1250413982bf-/root/npm,target=/root/.npm npm ci

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

npm warn deprecated read-package-json@6.0.4: This package is no longer supported. Please use @npmcli/package-json instead.

npm warn deprecated npmlog@6.0.2: This package is no longer supported.

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

npm warn deprecated gauge@4.0.4: This package is no longer supported.

npm warn deprecated fstream@1.0.12: This package is no longer supported.

npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.

npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs

npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported

npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported

npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported

npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported

npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported

npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

npm warn deprecated puppeteer@21.11.0: < 22.8.2 is no longer supported

[stage-0 4/9] RUN nix-env -if .nixpacks/nixpkgs-5624e1334b26ddc18da37e132b6fa8e93b481468.nix && nix-collect-garbage -d – CACHED

[stage-0 4/9] RUN nix-env -if .nixpacks/nixpkgs-5624e1334b26ddc18da37e132b6fa8e93b481468.nix && nix-collect-garbage -d ✔ 0ms – CACHED

Build timed out

View Deploy details

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

0 Replies

Loading...