[bitnami/mongodb] Unable to deploy

[Nahum48]

Name and Version

bitnami/mongodb 13.9.4

What architecture are you using?

amd64

What steps will reproduce the bug?

When I'm deploying the helm chart of MongoDB on my k3s, it's not finishing the deployment. I'm working on a test VM using K3. I have enough resources (7 cpu cores, and 9gb memory). no other apps are deployed in mt K3s, the MongoDB is the only one i want to install right now.

What is the expected behavior?

when i use the command: kubectl logs, and the pod name of the MongoDB, this is the result:
mongodb 10:26:33.03 
mongodb 10:26:33.03 Welcome to the Bitnami mongodb container
mongodb 10:26:33.04 Subscribe to project updates by watching https://github.com/bitnami/containers
mongodb 10:26:33.04 Submit issues and feature requests at https://github.com/bitnami/containers/issues
mongodb 10:26:33.04 
mongodb 10:26:33.04 INFO  ==> ** Starting MongoDB setup **
mongodb 10:26:33.06 INFO  ==> Validating settings in MONGODB_* env vars...
mongodb 10:26:33.33 INFO  ==> Initializing MongoDB...
mongodb 10:26:33.47 INFO  ==> Deploying MongoDB from scratch...
/opt/bitnami/scripts/libos.sh: line 344:    46 Illegal instruction     (core dumped) "$@" > /dev/null 2>&1

What do you see instead?

I sent you all the info i have...

Additional information

Currently this is is status of the pod:
default       my-mongodb-bc5fc94c4-968rp                     0/1     CrashLoopBackOff   17 (5s ago)      63m

[javsalgar]

Hi,

Which is the machine you are using to run Kubernetes? Is it a Mac M1 machine?

[Nahum48]

Hi,

It’s not a mac, I’m using ubuntu 20.04 image from osboxes.org (it’s a ready to use image without using an ISO file.

www.osboxes.orghttp://www.osboxes.org

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows

From: Javier J. @.> Sent: Monday, April 3, 2023 11:04 To: @.> Cc: @.>; @.> Subject: Re: [bitnami/containers] [bitnami/mongodb] Unable to deploy (Issue bitnami/charts#15951)

Hi,

Which is the machine you are using to run Kubernetes? Is it a Mac M1 machine?

— Reply to this email directly, view it on GitHubhttps://github.com/bitnami/charts/issues/15951, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOXKI4SJSNWXLSVIACV7VGTW7KAB3ANCNFSM6AAAAAAWQHFUMY. You are receiving this because you authored the thread.Message ID: @.***>

[mike-pisman]

Same issue, installed via portainer on Truenas Scale with bitnami charts.

[igorlidin]

Same issue, virtual machine with kvm64 cpu on Proxmox VE

[aoterolorenzo]

Hi @Nahum48, @mike-pisman , @igorlidin

Are you setting BITNAMI_DEBUG to true through the values or via env var?

This error is familiar to us, since it used to happen in ARM architectures using the amd64 containers. Could you ensure that your host machine architecture matches your VM architecture and the chart images?

[felix-appsmith]

Hello, I get this same error when executing the mongodb of my appsmith instance when doing the deployment, the only instances that fail are those of mongo with the same error described above attached the logs and my architecture.

Architecture: x86_64

appsmith-mongodb-0 LOGS:

mongodb 22:45:20.64 INFO  ==> Advertised Hostname: appsmith-mongodb-0.appsmith-mongodb.default.svc.cluster.local
mongodb 22:45:20.64 INFO  ==> Advertised Port: 27017
mongodb 22:45:20.65 INFO  ==> Data dir empty, checking if the replica set already exists
MongoNetworkError: getaddrinfo ENOTFOUND appsmith-mongodb-0.appsmith-mongodb-headless.default.svc.cluster.local
mongodb 22:45:21.47 INFO  ==> Pod name matches initial primary pod name, configuring node as a primary
mongodb 22:45:21.48 
mongodb 22:45:21.48 Welcome to the Bitnami mongodb container
mongodb 22:45:21.48 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mongodb
mongodb 22:45:21.48 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mongodb/issues
mongodb 22:45:21.49 
mongodb 22:45:21.49 INFO  ==> ** Starting MongoDB setup **
mongodb 22:45:21.50 INFO  ==> Validating settings in MONGODB_* env vars...
mongodb 22:45:21.55 INFO  ==> Initializing MongoDB...
mongodb 22:45:21.58 INFO  ==> Deploying MongoDB from scratch...
/opt/bitnami/scripts/libos.sh: line 336:    65 Illegal instruction     "$@" > /dev/null 2>&1

appsmith-mongodb-arbiter-0 LOGS:

mongodb 22:45:28.65 
mongodb 22:45:28.65 Welcome to the Bitnami mongodb container
mongodb 22:45:28.65 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mongodb
mongodb 22:45:28.65 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mongodb/issues
mongodb 22:45:28.65 
mongodb 22:45:28.65 INFO  ==> ** Starting MongoDB setup **
mongodb 22:45:28.66 INFO  ==> Validating settings in MONGODB_* env vars...
mongodb 22:45:28.68 INFO  ==> Initializing MongoDB...
mongodb 22:45:28.70 INFO  ==> Deploying MongoDB from scratch...
/opt/bitnami/scripts/libos.sh: line 336:    43 Illegal instruction     "$@" > /dev/null 2>&1

I'm running this on a laptop.

Any ideas?

[aoterolorenzo]

Since this doesn't seem trivial to solve, I will create an internal task for the team to address it. We will reach you back here as soon as we can (have in mind we can give an exact ETA, since it depends on the team workload). Meanwhile, I will mark the issue as on-hold.

[felix-appsmith]

Thank you very much, I really appreciate it.

The operating system I'm using is Pop OS 22.04.

[jdollar]

Unsure if this will help anyone, but after seeing this issue I also found this one here: https://github.com/bitnami/charts/issues/12834

which lead me, because I was noticing the issue on nodes running as VMs in Proxmox, to this forum post about getting avx capabilities passed to the VMs in Proxmox: https://forum.proxmox.com/threads/avx2-and-avx-flags-on-vm.87808/

For me, in order to get the mongodb chart to deploy on a K3S node that was running on a VM in Proxmox I had to change my processor type to be host instead of the default kvm64. So I guess that might help the people running the VMs. For the bare metal laptops I'd just check /proc/cpuinfo to see if avx is an enabled flag out there for your processor since it sounds like that is a requirement for the current mongodb build.

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions[bot]]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[kenneaal]

This just occurred again on an install of Meshcentral on TrueNAS SCALE. 2023-09-21 17:18:49.831466+00:00/opt/bitnami/scripts/libos.sh: line 346: 39 Illegal instruction "$@" > /dev/null 2>&1

Seems this must be reopened and investigated further.

[pbennett]

This error is familiar to us, since it used to happen in ARM architectures using the amd64 containers. Could you ensure that your host machine architecture matches your VM architecture and the chart images?

I'm getting this issue now on my M1 trying to use both bitnami/mongodb:6.0 and 7.0 seeing the error: /opt/bitnami/scripts/libos.sh: line 346: 48 Illegal instruction "$@" > /dev/null 2>&1

[pythoninthegrass]

Same as @pbennett. Since I can't use an arm image, set docker-compose.yml to platform: linux/amd64. Otherwise get the error:

λ docker compose up
[+] Running 0/2
 ⠙ db-dest Pulling                                                                                                                                                                                                                                                                                                                                                     1.0s
 ⠙ db-src Pulling                                                                                                                                                                                                                                                                                                                                                      1.0s
image with reference docker.io/bitnami/mongodb:6.0.10-debian-11-r17 was found but does not match the specified platform: wanted linux/arm64, actual: linux/amd64

Hard-coding the linux/amd64 platform raises this error:

λ docker compose up
[+] Running 2/2
 ✔ db-dest Pulled                                                                                                                                                                                                                                                                                                                                                      1.1s
 ✔ db-src Pulled                                                                                                                                                                                                                                                                                                                                                       1.1s
[+] Building 0.0s (0/0)                                                                                                                                                                                                                                                                                                                                     docker:orbstack
[+] Running 2/2
 ✔ Container copy_mongodb-db-dest-1  Recreated                                                                                                                                                                                                                                                                                                                         0.1s
 ✔ Container copy_mongodb-db-src-1   Recreated                                                                                                                                                                                                                                                                                                                         0.1s
Attaching to copy_mongodb-db-dest-1, copy_mongodb-db-src-1
copy_mongodb-db-src-1   | mongodb 22:50:16.61
copy_mongodb-db-dest-1  | mongodb 22:50:16.61
copy_mongodb-db-src-1   | mongodb 22:50:16.64 Welcome to the Bitnami mongodb container
copy_mongodb-db-dest-1  | mongodb 22:50:16.64 Welcome to the Bitnami mongodb container
<SNIP>
copy_mongodb-db-dest-1  | mongodb 22:50:17.37 INFO  ==> Deploying MongoDB from scratch...
copy_mongodb-db-src-1   | /opt/bitnami/scripts/libos.sh: line 346:   110 Illegal instruction     "$@" > /dev/null 2>&1
copy_mongodb-db-dest-1  | /opt/bitnami/scripts/libos.sh: line 346:   110 Illegal instruction     "$@" > /dev/null 2>&1
copy_mongodb-db-src-1 exited with code 132
copy_mongodb-db-dest-1 exited with code 132

Any plans to support arm macs on the roadmap? Happy to test custom image builds if you'd like!

OS: macOS 12.5 (21G72) Hardware: MacBook Pro (13-inch, M2, 2022)

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions[bot]]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[borainceler]

what's the solution?

[welkson]

Mongo v5 requires AVX (CPU): https://www.mongodb.com/pt-br/docs/v5.0/administration/production-notes/

"MongoDB 5.0 requires use of the AVX instruction set, available on select Intel and AMD processors."