I encountered an issue while setting up my Docker Compose environment (Ignition, MySQL, and SMTP server) for training. I'm automating the upload of the MySQL JDBC driver by mounting the file directly to the expected JDBC path in my Ignition container. However, placing the .jar file directly at the …

You should be able to bind-mount that specific driver all the way into place, e.g.: - ./jdbc/mysql-connector-j-8.3.0.jar:/usr/local/bin/ignition/user-lib/jdbc/mysql-connector-j.jar By bind-mounting the entire folder, you effectively shadow the pre-existing files that are part of the image (such as…

Consider preloading a gateway backup--that contains the JDBC drivers and metadata for them from the source system.

Appreciate the feedback. I'll be sure to use this approach going forward. Just wanted to double-check that I wasn't overlooking a step in my original attempt using a volume mount.

[image] kcollins: mage (such as the MariaDB, Postgr I have just verified this suggestion and it worked. Thank you!

Tangent to the main question posed, worth noting that you probably also don't need the MySQL driver at all. The MariaDB driver (as far as I know) is able to connect to MySQL no problem.

I have found that the Maria driver performs better as well. We switched a customer from the MySQL to Maria driver and got more than 10% CPU back (we are really really heavy DB users). Some performance comparisons that may or may not be biased. [image] MariaDB Java Connector Driver Perfor…