When try to migrate to Meteor 3 on CentOs 8, I’m getting the following error even though the documentation specifies that Meteor is compiled under CentOS 6.4 for compatibility purpose.
Have I misunderstood the documentation (Install | Docs)?
Thanks.
Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.26’ not found (required by /home/developer/.meteor/packages/meteor-tool/.3.0.4.aaa58r.y4jxf++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/vscode-nsfw/build/Release/nsfw.node)
at Object.Module._extensions…node (node:internal/modules/cjs/loader:1586:18)
at Module.load (node:internal/modules/cjs/loader:1288:32)
at Module.Mp.load (/tools/static-assets/server/runtime.js:35:31)
at Function.Module._load (node:internal/modules/cjs/loader:1104:12)
at Module.require (node:internal/modules/cjs/loader:1311:19)
at Module.mod.require (/home/developer/.meteor/packages/meteor-tool/.3.0.4.aaa58r.y4jxf++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/@meteorjs/reify/lib/runtime/index.js:30:33)
at require (node:internal/modules/helpers:179:18)
at Object. (/home/developer/.meteor/packages/meteor-tool/.3.0.4.aaa58r.y4jxf++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/vscode-nsfw/js/src/index.js:4:14)
at Module._compile (node:internal/modules/cjs/loader:1469:14)
at Module.Mp._compile (/tools/static-assets/server/runtime.js:78:21) {
code: ‘ERR_DLOPEN_FAILED’
}
I’m not very familiar with that OS. As we update Node, Mongo, and other tools in Meteor, the requirements for native libraries are changing. It’s our mistake to include CentOS 8 compatibility if it doesn’t work. I’ll need to verify in a Virtual Machine.
By the way, is Meteor 2 working on your CentOS 8? Do you have access to a newer version of CentOS? Could you test it? I’ll set up a VM to help, as we may need to update the docs.
It seems that this is a package missing or needing an update ( here shown in 7 also ) and with modification to the version needed, a solution like this might work?
Not necessarily OS incompatibility, just build environment no longer updated by the OS package dependency management as recently. Curious if that fixes it. I had issues like this with alpine versus debian in container image builds as well, and it is often just a build environment modification needed.
Have you tried developing on other distro, like newest Ubuntu, and then building Docker container with Ubuntu base image, and running that container with Docker at CentOS ?
If it is old hardware, where CPU does not support AVX, that MongoDB 5 and newer requires, it’s possible to run MongoDB at Qemu that supports AVX:
It’s possible to check CPU support for AVX this way: