-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: child process failed, exited with 51 #606
Comments
Same problem w/ tags 6.0 and 6.0.4 here. I picked tag 5.0 randomly and it worked. |
Any other logs you can provide that might be helpful? A more reliable reproducer? (I'm not able to reproduce myself 🙈) |
This is happening to us also. It began with version 6.0.4. This seems to be when Ubuntu was switched from It is the mongod command in docker-entrypoint.sh that is exiting with code 51. This is the output from manually running the mongod command:
Without the --fork:
I thought it might have something to do with filesystem, but one system has xfs and another has ext4 on the partition where the volume is. They both fail. When starting a container with 6.0.4 with a previously created and working data_db volume, there is this error instead:
|
I wonder if https://www.mongodb.com/docs/manual/administration/production-notes/#x86_64 got a bump in requirements but it wasn't documented yet? 😬 Can someone who can reproduce run |
🤔 This is possibly host |
The 22:20:24.297 message is "Multi threading initialized". Then the .298 messages are the "Writing fatal message" ones. |
Confirmed that the issue does not happen with docker option It also does not happen with
but does happen with
|
Thanks for confirming. This is similar to the issue in Alpine 3.14 images when they started using a new syscall: |
Same issue when running containers on CircleCI... Switching to |
Same problem here and as @lindelius comment, switching to |
The "correct" solution is to update Docker, runc, and libseccomp on your host, but downgrading is a fine temporary solution (I wouldn't recommend it long term or for production workloads since we aren't actively maintaining that |
it's very helpful thanks |
Running the latest docker image (image id: a440572ac3c1 / tag 6.0.4 or latest) by using docker compose the process fails with the following error:
ERROR: child process failed, exited with 51
My docker compose file
Using image tag =<6.0.3 everything works fine.
The text was updated successfully, but these errors were encountered: