No matter what I do retooldb uses virtual conainer and NOT my external cluster

💬 Self Hosted Retool
1

  1. My goal:For Retool to use actual environment variables to connect to Retool db using them. Instead it uses retooldb-postgres:5432/ even when I removed this container from compose.yaml and specified credentials in retooldb.env

  2. What I’ve tried so far: tried moving # Retool DB credentials into main docker.env and back to retooldb.env. It ignores them. I assume the issue may be that I have initially created a Retool instance, and the RetoolDB was a container. But then I decided to migrate to an external cluster, but it got cached somehow within the Retool, and now it only looks for local containers or creates them automatically.

  3. I have also tried deleting from the postgres database the row from resources about Retool database. Nothing helps. Now there is no container. I have external credentials within the environment file. I have restarted the server like five times. But when I open resources and open RetoolDB, it still somehow opens something even though there is no freaking container. And it still works, but it is not my external database, which is very annoying.

    Screen 2025-10-11 at 11.45.46@2x
    Screen 2025-10-11 at 11.45.46@2x834×108 31.1 KB