RafalWilinski / telegram-chatgpt-concierge-bot

Interact with OpenAI's ChatGPT via Telegram and Voice.
https://chatwithcloud.ai
1.13k stars 109 forks source link

deploy failure on Railway #11

Open iamqiuxuan opened 1 year ago

iamqiuxuan commented 1 year ago

what should i do

erbanku commented 1 year ago

+1 Error Message:


==============
Using Nixpacks
==============
context: 0f87d1cec980d51395adce27b23b1231

╔═══════════════════════════════ Nixpacks v1.5.1 ══════════════════════════════╗
║ setup      │ ffmpeg, libnss3, libatk1.0-0, libatk-bridge2.0-0, libcups2,     ║
║            │ libgbm1, libasound2, libpangocairo-1.0-0, libxss1, libgtk-3-0,  ║
║            │ libxshmfence1, libglu1                                          ║
║──────────────────────────────────────────────────────────────────────────────║
║ install    │ npm ci                                                          ║
║──────────────────────────────────────────────────────────────────────────────║
║ build      │ npm install                                                     ║
║──────────────────────────────────────────────────────────────────────────────║
║ start      │ npm start                                                       ║
╚══════════════════════════════════════════════════════════════════════════════╝

#1 [internal] load .dockerignore
#1 transferring context: 2B done

#1 DONE 0.0s

#2 [internal] load build definition from Dockerfile
#2 transferring dockerfile: 2.38kB done
#2 DONE 0.0s

#3 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1678752204

#3 DONE 0.2s

#4 [stage-0  1/10] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1678752204@sha256:fba77818e57bebd4e7a02f60d45554354d6ec5a3f7d98b4ee4f6b2a6e720191e
#4 DONE 0.0s

#5 [internal] load build context
#5 transferring context: 787.31kB done

#5 DONE 0.0s

#6 [stage-0  2/10] WORKDIR /app/
#6 CACHED

#7 [stage-0  3/11] COPY .nixpacks/nixpkgs-293a28df6d7ff3dec1e61e37cc4ee6e6c0fb0847.nix .nixpacks/nixpkgs-293a28df6d7ff3dec1e61e37cc4ee6e6c0fb0847.nix
#7 CACHED

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

#9 [stage-0  5/11] RUN apt-get update && 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
#9 CACHED

#10 [stage-0  6/11] RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile

#10 DONE 0.6s

#11 [stage-0  7/11] COPY . /app/.
#11 DONE 0.0s

#12 [stage-0  8/11] RUN --mount=type=cache,id=s/b4252536-2e2a-4708-a44d-c09552097023-/root/npm,target=/root/.npm npm ci

#12 0.400 /bin/bash: line 1: npm: command not found

#12 ERROR: process "/bin/bash -ol pipefail -c npm ci" did not complete successfully: exit code: 127
-----
> [stage-0  8/11] RUN --mount=type=cache,id=s/b4252536-2e2a-4708-a44d-c09552097023-/root/npm,target=/root/.npm npm ci:
#12 0.400 /bin/bash: line 1: npm: command not found
-----

Dockerfile:21
lorrylockie commented 1 year ago

same here

victorlavadoalva commented 1 year ago

i solve it by deleting my package-lock.json, them i use "npm i", finally push it to the main

Gaguilera98 commented 11 months ago

helpme

8 18.09 installing '5148520bfab61f99fd25fb9ff7bfbb50dad3c9db-env'

8 18.92 error:

8 18.92 … while calling the 'derivationStrict' builtin

8 18.92

8 18.92 at /builtin/derivation.nix:9:12: (source not available)

8 18.92

8 18.92 … while evaluating derivation '5148520bfab61f99fd25fb9ff7bfbb50dad3c9db-env'

8 18.92 whose name attribute is located at /nix/store/lgcjj6s23v2203zyihsd0j26wh1saj0c-source/pkgs/stdenv/generic/make-derivation.nix:300:7

8 18.92

8 18.92 … while evaluating attribute 'passAsFile' of derivation '5148520bfab61f99fd25fb9ff7bfbb50dad3c9db-env'

8 18.92

8 18.92 at /nix/store/lgcjj6s23v2203zyihsd0j26wh1saj0c-source/pkgs/build-support/trivial-builders/default.nix:88:7:

8 18.92

8 18.92 87| inherit buildCommand name;

8 18.92 88| passAsFile = [ "buildCommand" ]

8 18.92 | ^

8 18.92 89| ++ (derivationArgs.passAsFile or []);

8 18.92

8 18.92 error: php80 has been dropped due to the lack of maintenance from upstream for future releases

8 ERROR: process "/bin/bash -ol pipefail -c nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d" did not complete successfully: exit code: 1


[ 4/12] RUN nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d:

18.92 … while evaluating attribute 'passAsFile' of derivation '5148520bfab61f99fd25fb9ff7bfbb50dad3c9db-env'

18.92

18.92 at /nix/store/lgcjj6s23v2203zyihsd0j26wh1saj0c-source/pkgs/build-support/trivial-builders/default.nix:88:7:

18.92

18.92 87| inherit buildCommand name;

18.92 88| passAsFile = [ "buildCommand" ]

18.92 | ^

18.92 89| ++ (derivationArgs.passAsFile or []);

18.92

18.92 error: php80 has been dropped due to the lack of maintenance from upstream for future releases


Dockerfile:8


6 |

7 | COPY .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix

8 | >>> RUN nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d

9 |

10 | COPY .nixpacks/assets /assets/


ERROR: failed to solve: process "/bin/bash -ol pipefail -c nix-env -if .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix && nix-collect-garbage -d" did not complete successfully: exit code: 1

Error: Docker build failed

abdulazeez761 commented 10 months ago

i solve it by deleting my package-lock.json, them i use "npm i", finally push it to the main

it worked for me Thx

mrzewnicki commented 10 months ago

Any solution on that? I'm also facing with same issue

imvinojanv commented 8 months ago

i solve it by deleting my package-lock.json, them i use "npm i", finally push it to the main

I also facing this issue while I deploy the Next.js application on railway.app I am getting the same error, How can I fix this error, I have tried with deleted the package-log file and re-install npm as well, it's not working. Give me the solution.

angllovera commented 4 months ago

[Region: us-west1]

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

Using Nixpacks

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

context: 3500f4cbebb03c3ee19dffab5c8525bc

╔══════════════════════════════ Nixpacks v1.24.0 ══════════════════════════════╗

║ setup │ (php80.withExtensions (pe: pe.enabled ++ [])), nginx, ║

║ │ libmysqlclient, php80Packages.composer, nodejs_18, npm-9_x ║

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

║ install │ mkdir -p /var/log/nginx && mkdir -p /var/cache/nginx ║

║ │ composer install --ignore-platform-reqs ║

║ │ npm ci ║

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

║ build │ composer install && npm install --production && php artisan ║

║ │ optimize && php artisan config:chache && php artisan ║

║ │ route:cache && php artisan view:cache && php artisan migrate ║

║ │ --force ║

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

║ start │ node /assets/scripts/prestart.mjs /assets/nginx.template.conf ║

║ │ /nginx.conf && (php-fpm -y /assets/php-fpm.conf & nginx -c ║

║ │ /nginx.conf) ║

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

0 building with "default" instance using docker driver

1 [internal] load build definition from Dockerfile

1 transferring dockerfile: 3.71kB done

1 DONE 0.1s

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

2 DONE 0.1s

3 [stage-0 1/10] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1716249803@sha256:5ef4d2021c418fcaabb56cea5ea9e24a5fdedfe27f58062d9689214dfed45c46

3 DONE 0.0s

4 [stage-0 2/10] 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: 6.88MB 0.1s done

6 DONE 0.1s

7 [ 3/12] COPY .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix .nixpacks/nixpkgs-5148520bfab61f99fd25fb9ff7bfbb50dad3c9db.nix

tengo el mismo problema

jmsherry commented 3 weeks ago

I fixed this issue by upgrading to node v.18.