DukeLeTran replied
actually when u run this docker compose, u r provisioning a mariadb container and it sets your credential up based on the environment variables
âI did pre-create âapp_nocodbâ priorâ
so why did u pre-create? it sounds like u r creating another DB
I did create a new DB, along with the new credentials (i.e. âapp_nocodbâ) â mostly because I thought it was required
**without **my pre-made database/credentials, it does spin up, but I do **not **see the âroot_dbâ database show up in my mariadb though mysql -u noco -p; SHOW DATABASES; so where would that database be?
i think i know wtâs happened.
when u said u created a new DB, it is actually on your local, not docker container. In your docker compose, you are actually referring to the DB in the docker container. i.e. you create the DB & NocoDB when u run docker-compose up.
when u said u didnât see root_db, i think you are looking at the local one instead of the the docker one. You can use docker exec command to get into the container. In the container, run mysql -u noco -p and enter your password n check your databases. (thatâs wt i did in screenshot)
in summary, thereâs sth u need to consider.
1. which database u need to use for nocodb? either the one on your local or the one on docker
2. if you want to use your local db, then you donât need to use docker-compose
3. if you want to use existing docker db, then you dont need to use docker-compose
4. if you want to use docker db which is provisioned with nocodb, then use docker-compose
makes sense â thank you so much!!