Strapi build fails
sashapop10
HOBBYOP

2 years ago

After migration of my postgresql database i recieving next error:
31.71 Node.js configure: Found Python 3.11.5…

31.71 Please use python3.10 or python3.9 or python3.8 or python3.7 or python3.6 or python3.5 or python2.7.

32.33 error: builder for '/nix/store/hh8n2lf9hxvjrp2rgp6542acrcyg153i-nodejs-14.21.3.drv' failed with exit code 1

32.35 error: 1 dependencies of derivation '/nix/store/hr6azazr0rnipm5vda93z8fql7d6q20a-bf744fe90419885eefced41b3e5ae442d732712d-env.drv' failed to build

Dockerfile:8

6 |

7 | COPY .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix

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

9 |

10 |

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

Error: Docker build failed

How can i fix it ? My production website dead..

Archived

6 Replies

sashapop10
HOBBYOP

2 years ago

I think problem with nodejs, but how can i change version in railway ?


sashapop10
HOBBYOP

2 years ago

Problem solved with upgrading nodejs :(


bublinec
HOBBY

2 years ago

Hello, to what version have you upgraded please? Is that strapi v3?


sashapop10
HOBBYOP

2 years ago

Lucky for me - my strapi version was v4. To fix that issue i just manualy setup by railway.toml nixpacksVersion = "1.17.0", and updated my nodejs version from v14 to latest at v16.


Status changed to Solved Railway about 2 years ago


sashapop10
HOBBYOP

2 years ago

I think that core problem at nixpacks, nodejs v14 depends on unsupported python version. Migrating Strapi to newer version usualy painful, especially if you depended by opensource library that stacked on Strapi v3.

You can try to do experement with Dockerfile, it will pull nodejs from Docker registry and will avoid nix store if i think correctly. For my case it wasn't fast enough solution because of production failure, and i fixed it straight. I didn't tried it, but you have pretty solid chances with that.


sashapop10
HOBBYOP

2 years ago

I hope nodejs v16 will live forever here =)


Status changed to Archived Railway over 1 year ago


Loading...