shadysamir
shadysamir
I was wondering in #540 if this is still going forward. We came across is today and honestly speaking there is nothing else similar to it everywhere we looked.
To verify the issue is not related to coolify, I created my own nodejs mini app inside the same project and tested the connection json with pg and with knex....
@dstala this is my own thread over there. And it's not resolved. I tested knex library in my own application and it worked. But it still can't resolve the db...
@dstala I think I do not have the permission to reopen the issue.
I tried the solution provided by the bot in the comments and added `NODE_OPTIONS="--dns-result-order=ipv4first"` env variable. Still nocodb is unable to resolve the db container name
Solved by setting "use provided network" in coolify nocodb application settings.