R
Railway5mo ago
Zef

Can no longer build projects - `GLIBC_2.36' not found

Hey we have started to see the following error during deployment across all the services in our project.
#12 68.00 .../node_modules/@prisma/engines postinstall: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6)



#12 68.00 .../@intlify/vue-i18n-bridge postinstall: Failed

#12 68.04 .../node_modules/@nestjs/core postinstall: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6)

#12 68.04 .../node_modules/@nestjs/core postinstall: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6)



#12 ERROR: process "/bin/bash -ol pipefail -c pnpm i --frozen-lockfile" did not complete successfully: exit code: 1
#12 68.00 .../node_modules/@prisma/engines postinstall: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6)



#12 68.00 .../@intlify/vue-i18n-bridge postinstall: Failed

#12 68.04 .../node_modules/@nestjs/core postinstall: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6)

#12 68.04 .../node_modules/@nestjs/core postinstall: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /nix/store/9fy9zzhf613xp0c3jsjxbjq6yp8afrsv-gcc-12.3.0-lib/lib/libstdc++.so.6)



#12 ERROR: process "/bin/bash -ol pipefail -c pnpm i --frozen-lockfile" did not complete successfully: exit code: 1
I have seen one other person has had a similar issue and was advised to use a custom docker image as a workaround. This isn't really a desirable option for us as we have 10 services, and changing the underlying docker is a pretty big and risky change! We assumed there has been an update to nixpacks that has introduced this error so we have tried downgrading to the previous nixpack version but got the same problem.
11 Replies
Percy
Percy5mo ago
Project ID: 22264c73-119a-41cd-97a8-43fccaf63d28
Zef
Zef5mo ago
22264c73-119a-41cd-97a8-43fccaf63d28
Brody
Brody5mo ago
was the downgrade successful?
Zef
Zef5mo ago
No it wasn't we got the same error
Brody
Brody5mo ago
sorry I mean, did you confirm that indeed an older version of nixpacks was not being used
Zef
Zef5mo ago
Yes we could see the version being used in the build logs
Zef
Zef5mo ago
We are specifying the version like this
No description
Brody
Brody5mo ago
isn't that the latest version?
Zef
Zef5mo ago
no that is one behind I believe
devi4nt
devi4nt5mo ago
@Zef - ended up using 1.21.0 in the end, 1.21.1 exhibited the same build error.
Brody
Brody5mo ago
yes you are correct, my bad. and I was just gonna suggest going another version back haha