MongoDB fails to start

[vvarga007]

Describe the bug

MongoDB fails to run as it cannot create a lock file under /var/lib/mongodb/data.
A chown solved the problem, would it be worth adding it to the MongoDB deployment template?
Or an init container.

lifecycle:
  postStart:
    exec:
      command:
        - /bin/sh
        - '-c'
        - chown mongodb:mongodb -R /var/lib/mongodb

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Microcks version or git rev

No response

Install method (docker-compose, helm chart, operator, docker-desktop extension,...)

No response

Additional information

No response

[github-actions]

👋 @vvarga007

Welcome to the Microcks community! 💖

Thanks and congrats 🎉 for opening your first issue here! Be sure to follow the issue template or please update it accordingly.

📢 If you're using Microcks in your organization, please add your company name to this list. 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

If you need to know why and how to add yourself to the list, please read the blog post "Join the Microcks Adopters list and Empower the vibrant open source Community 🙌"

Hope you have a great time there!

🌟 ~~~~~~~~~ 🌟

📢 If you like Microcks, please ⭐ star ⭐ our repo to support it!

🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

[lbroudoux]

Hey @vvarga007
Could it be related to #109 that we fixed by applying config as described in #58?

I love your suggestion better but I wonder how it behaves on platforms like OpenShift where UIDs and GUID are randomized within a range... (see https://www.redhat.com/en/blog/a-guide-to-openshift-and-uids). I think the same logic applied to mounted files in OpenShift and so my fear is to break stuff there if we change owner this way...

What do you think? Any people with OpenShift knowledge or ability to test on OpenShift?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️