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 designated location caused the other drivers to appear faulted. Even though MySQL was listed as installed, I couldn't establish a successful connection to my database.
As a test, I set up the same Docker stack without the volume mount, which allowed me to observe the default state of installed or faulted drivers. I then manually uploaded the .jar file from my host machine and attempted a connection, which succeeded.
Currently, my workaround is to upload the file during container creation, ensuring the gateway has the necessary driver for MySQL.
Any insights on why directly mounting the file causes issues with other drivers and connection establishment?
- ./jdbc:/usr/local/bin/ignition/user-lib/jdbc/
Impact of Direct JDBC Mounting: Faulted Drivers in Ignition Gateway
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.
By bind-mounting the entire folder, you effectively shadow the pre-existing files that are part of the image (such as the MariaDB, Postgres, and MSSQL JDBC drivers, as well as the commons-dbcp2 and commons-pool2 JARs).
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.
And you have the advantage of not having to deal with extra licensing terms.
