DocHub | Baidu Library , an open source library system

Alpine uses musl for its C library. You can either use a different non-alpine based image such as node:12-buster-slim or any of the other non-Alpine tags here, or try to get it to work by setting up glibc with the instructions here. Using a Debian or Ubuntu based image would be the easiest way forward.

This log output is called "structured log output" and is the only log format of MongoDB as of 4.4. Previous versions used the human-readable log format.

There are tools under development to make this log output human-readable:

• https://github.com/markbenvenuto/mrlog
• Another one that I can't recall at the moment

mongod process by default binds only to the localhost interface

This is inaccurate. If you look inside the container:

1. start with removing all PPA repositories for mongodb, then:
2. sudo apt-get purge mongodb-org*
3. sudo apt remove mongodb
4. sudo apt purge mongodb
5. sudo apt autoremove
6. sudo rm -r /var/log/mongodb
7. sudo rm -r /var/lib/mongodb
8. sudo apt-get install gnupg
9. wget -qO - https://www.mongodb.org/static/pgp/server-4.4.asc | sudo apt-key add -
10. echo "deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/4.4 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-4.4.list
11. sudo apt-get update
12. sudo apt-get upgrade
13. sudo apt update
14. sudo apt upgrade
15. sudo apt-get install -y mongodb-org
16. sudo apt-get install libc6
17. sudo service mongod start
18. sudo service mongod status

This helped me with the issue

As suggested in the comments those kind of problems usually indicates issues with coredns and dns resolution. Is it worth to mention that Kubernetes documentation goes thru couple of good dns troubleshooting steps:

• Check the local DNS configuration first

"This version of MongoDB is too recent to start up on the existing data files. Try MongoDB 4.2 or earlier."

Logs above indicate you have to downgrade to MongoDB 4.2 or earlier

Since your existing data was created using MongoDB version <= 4.2

Try downgrading to 4.2 and see if it works.

A stored WiredTiger version of 3.3 means the data files were written by a MongoDB version from 4.2.6 to 4.2.8.

One of those versions should be able to open those files.

Turns out it's a bug in version 4.4:

https://jira.mongodb.org/browse/WT-6623

Thanks for reporting the issue. Having a look at the information provided it appears that a bug was introduced in WT-6374. On upgrade to 4.4, WiredTiger creates a file to track history, the file id of this file was incorrectly allocated and is overlapping with a preexisting file. Which results in the error seen.

We're working on a fix and will provide updates and respond with further steps.

özkan pakdil pointed me to another post which held the answer. The default database location is /tmp and it does not persist there. I added the spring property, in application.properties: spring.mongodb.embedded.storage.database-dir=/home/craig/mongodb/ and it now persists cross-session. Job done!