[Bug]: Changing default configuration does not work

[hkad98]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I have a docker-compose file where I defined the mindsdb service as follows:

 mindsdb:
    image: mindsdb/mindsdb:22.11.3.2
    ports:
      - "47334:47334"
      - "47335:47335"
      - "47336:47336"
    environment:
      MDB_CONFIG_CONTENT: '{"api": {"mysql": {"host": "0.0.0.0", "password": "mindsdb", "port": "47335", "user": "mindsdb", "database": "mindsdb", "ssl": true}}}'
    volumes:
      - mindsdb-data:/data

I need to override the default password for MySQL, which I do by setting the environment variable MDB_CONFIG_CONTENT with the override password for MySQL.

When I start the docker-compose, all services are up and running. MySQL starts, and I can connect there with an override password. The issue is when I see the start-up of HTTP in logs.

2022-11-16 11:39:57,307 - WARNING - check auth, user=mindsdb: password mismatch
2022-11-16 11:39:57,309 - WARNING - Access denied for user mindsdb
2022-11-16 11:40:24,452 - WARNING - check auth, user=mindsdb: password mismatch
2022-11-16 11:40:24,454 - WARNING - Access denied for user mindsdb
2022-11-16 11:40:29,643 - WARNING - check auth, user=mindsdb: password mismatch
2022-11-16 11:40:29,645 - WARNING - Access denied for user mindsdb

Therefore http://localhost:47334/ does load and ends with the error message ERR_EMPTY_RESPONSE.

Expected Behavior

I expect that overriding MySQL password will not break http.

Steps To Reproduce

Run docker or docker-compose with an override password for MySQL and try to open http://localhost:47334.

MDB_CONFIG_CONTENT: '{"api": {"mysql": {"host": "0.0.0.0", "password": "mindsdb", "port": "47335", "user": "mindsdb", "database": "mindsdb", "ssl": true}}}'

Anything else?

No response

[ZoranPandovski]

Hi @hkad98, sorry for the late response. If you start the container with the following:

MDB_CONFIG_CONTENT: '{"api": {"mysql": {"host": "0.0.0.0", "password": "mindsdb", "port": "47335", "user": "mindsdb", "database": "mindsdb", "ssl": true}}}'

This will only start the MySQL API. The HTTP API will not start since it does not exist in the config. If you want to run the HTTP API too, you will need to include it in the config.

[hkad98]

Hi @ZoranPandovski,

Thanks for your reply. Could you please extend documentation with this information? This behavior is not fully explained in the documentation. From the documentation, I understand that MDB_CONFIG_CONTENT will override values for passed keys, which I think is straightforward. Still, the actual behavior is different and unclear – for the change of MySQL password, I need to copy-paste the whole config and change the only value for the password.

[ZoranPandovski]

Yes, that makes sense. I will add info in docs for now and include this as an enhancement so we can handle that better.