Closed Anticom closed 2 years ago
FYI: I'm experiencing the same issue with bitnami/mongodb-sharded (chat version 5.0.8)
i might be wrong, but i read that ARM64 is entirely NOT supported.
@jmConan I would have thought that the container would refuse to start if the platform was the issue. (See docker/for-mac#6137 for example, which is a common issue for lots of amd64 images.) Either way IMHO it would be nice to get some proper message out of the bitnami container rather than just stopping to log anything until being killed by k8s due to not becoming ready / alive within the set limits.
Hi, we have created this issue https://github.com/bitnami/charts/issues/7305 that is pinned in the Bitnami Helm Charts repository, on this way we can funnel all the conversation in a single place regarding ARM64 support. We will close the rest of the existing issues just to avoid duplications, please visit the above-mentioned issue to see any new (when possible) about this topic.
Name and Version
bitnami/mongodb 12.1.7
What steps will reproduce the bug?
Are you using any custom parameters or values?
No, using default parameters
What is the expected behavior?
MongoDB should start with standalone architecture.
What do you see instead?
mongodb pod starts but will never become ready. When looking at the logs, they never get past the last line in this snippet. After some time the pod will restart (due to probes failing presumably) and then the same happens over and over again:
Here's the environment inside the container:
Additional information
Please note that the events might be duplicated here and there since I was repeatedly re-installing the chart to figure out whether I could fix the issue myself by modifying some settings.