DB error 500 when running MySQL and CouchDBs alongside in a shared container

Wappler General Bugs
1

Wappler Version : Beta 1
Operating System : Win 11
Server Model: Node
Database Type: docker cloud local
Hosting Type: docker local

Expected behaviour

What do you think should happen?

MySQL based API actions should work

Actual behaviour

What actually happens?

500 error message

OK, the setup is quite complex

I have a docker base website linked to a container

image
image1205×980 22.7 KB

No database is defined for that container

I have 2 databases running in a separate container, one couch and one MySQL

image

which are running happily in docker

image
image2250×439 55.3 KB

I have two database connections defined

image

“db” points to the MySQL cloud (docker) MySQL database and connection test works OK

image
image744×964 26.4 KB

image
image738×322 11.9 KB

db_connection points to a cloud (docker) couch database

image
image732×955 23.8 KB

again test works

image

I also have both are similarly defined in workflows _> Globals → Connection Options

I can run the couchdb connection perfectly and manage couch/pouch entries

All good to now

image
image1881×750 53 KB

HOWEVER if i try to do anything from the “db” connection such as perform a database query, i get a long pause ( 5 seconds +) then an error message

{
status: "500",
code: "EAI_AGAIN",
message: "getaddrinfo EAI_AGAIN mysql",
stack: "Error: getaddrinfo EAI_AGAIN mysql
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
    --------------------
    at Protocol._enqueue (/opt/node_app/node_modules/mysql/lib/protocol/Protocol.js:144:48)
    at Protocol.handshake (/opt/node_app/node_modules/mysql/lib/protocol/Protocol.js:51:23)
    at Connection.connect (/opt/node_app/node_modules/mysql/lib/Connection.js:116:18)
    at /opt/node_app/node_modules/knex/lib/dialects/mysql/index.js:66:18
    at new Promise (<anonymous>)
    at Client_MySQL.acquireRawConnection (/opt/node_app/node_modules/knex/lib/dialects/mysql/index.js:61:12)
    at create (/opt/node_app/node_modules/knex/lib/client.js:262:39)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)"
}

Unless my logic regarding these connections is wrong, this appears to be a bug although i accept i have never tried to run 2 separate databases within the same container but believe this should be feasible?