Docker build gives Illegal Instruction (Core Dump) with Latest and v2.1.1 tag

[Illydth]

The docker build on my system is giving a "Illegal instruction (core dumped)" message upon running a docker build.

The break is at step 12 of 15 where it goes to run the mongo database, returns with a non-zero code of 132. That said, there's some broken stuff slightly up from there (step 10/15) and down.

Step 10/15 : RUN npm install
 ---> Running in 440d3d8f2c9f
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

> node@14.19.1 preinstall /data/db2/node_modules/node
> node installArchSpecificPackage

+ node-linux-x64@14.19.1
added 1 package in 8.252s
found 0 vulnerabilities

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1160 packages from 499 contributors and audited 1162 packages in 64.13s

73 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Removing intermediate container 440d3d8f2c9f
 ---> 955b92e8d4bf
Step 11/15 : COPY --chown=mongodb:mongodb . /data/db2/
 ---> 3698a675a51d
Step 12/15 : RUN mongod --fork --logpath /var/log/mongodb.log --dbpath /data/db2   && npm run db:refresh   && mongod --dbpath /data/db2 --shutdown   && chown -R mongodb /data/db2
 ---> Running in abb8170388c2
Illegal instruction (core dumped)
The command '/bin/sh -c mongod --fork --logpath /var/log/mongodb.log --dbpath /data/db2   && npm run db:refresh   && mongod --dbpath /data/db2 --shutdown   && chown -R mongodb /data/db2' returned a non-zero code: 132

Tried this with the 'latest' checkout from the 'main' branch and a checkout of v2.1.1 tag branch. My "mongo:latest" shows 3 weeks ago on a docker image ls. 5eAPI is working fine (built fine) but database isn't happy.

Any ideas?

[github-actions]

🎉 This issue has been resolved in version 2.1.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[bagelbits]

This is probably from us using mongo:latest. Though, I was having trouble testing since I'm on an M1 laptop now. It looks like locking us to Mongo 6.x.x got us going again.

[Illydth]

You guys rock, will test as soon as I get a moment.