Open duracell opened 9 months ago
Hello! You need admin rights to auto upgrade mongo. I will implement a way to bypass the upgrade process through env variable.
and how to configure it to with admin rights? even if temporarily?
I got it working this way:
MONGO_INITDB_ROOT_USERNAME
, MONGO_INITDB_ROOT_PASSWORD
for mongo docker containerMONGO_ENDPOINT=mongodb://mongo:27017/your_spotify
for application containeras mongo container readme says:
Security By default Mongo's configuration requires no authentication for access, even for the administrative user. See the "MONGO_INITDB_ROOT_USERNAME, MONGO_INITDB_ROOT_PASSWORD" section below for information on how to begin securing Mongo and the MongoDB Security documentation for more detail.
Describe the bug
After updating to the current version, the server docker is not starting because of problems with authorization at the mongo db instance. I set up a specific db and user for your_spotify and I'm not sure why it wants to write at the admin db (as far as I understand). Is there anything to prevent this or fix it, hopefully without granting complete admin right to the whole mongodb instance.
Expected behavior
Don't request admin rights on the mongo db instance.
Additional context
It seems midly similiar to #242.