Hi there, a question regarding custom SQLAlchemy DBs: I am wondering how the process of adding a custom SQLAlchemydriver to the Docker quickstart looks like. The info I got was to put the driver file into the

datahub-actions

image. However, unixODBC seems not to be present in that image. I saw

datahub-gms

references MySQLs JDBC driver. Would that be the appropriate image to put a custom driver file? Does both JDBC or ODBC work or only the first?

Hey @rich-salesmen-55640 we don't have a great way to inject custom drivers into the actions image, but we are thinking about it. Is your driver a pip or apt installable package?

Hi @mammoth-bear-12532 I was actually using the cli directly and wanted to go down the custom docker image route. But just to be clear, the driver needs to go into the

actions

image? It’s unfortunately not apt or pip installable, hence I was wondering how it’s gonna be discoverable for datahub to use.

yes the driver needs to be available to the actions image .. you can build an image that extends the base actions image and adds your driver on top.. and then run that container as the actions container