# Why no MariaDB driver with docker image

**URL:** <https://forum.inductiveautomation.com/t/why-no-mariadb-driver-with-docker-image/75261>\
**Category:** Ignition\
**Tags:** docker\
**Created:** [June 20, 2023, 11:36am UTC](https://forum.inductiveautomation.com/t/why-no-mariadb-driver-with-docker-image/75261 "2023-06-20T11:36:10Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eskil\_Holum](https://avatars.discourse-cdn.com/v4/letter/e/cdc98d/32.png) [@Eskil\_Holum](https://forum.inductiveautomation.com/u/Eskil_Holum)\
**Post date:** [June 20, 2023, 11:36am UTC](https://forum.inductiveautomation.com/t/why-no-mariadb-driver-with-docker-image/75261/1 "2023-06-20T11:36:10Z")

</div>

Hi, is there any reasoning for the MariaDB driver to not be included in the official docker image when it is normally bundeled with the installation files?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 20, 2023, 11:51am UTC](https://forum.inductiveautomation.com/t/why-no-mariadb-driver-with-docker-image/75261/2 "2023-06-20T11:51:34Z")

</div>

Many of the JDBC drivers were dropped from the standard install due to licensing issues. You can add it back yourself (as part of a gateway backup). CopyLeft licenses create peculiar corner cases when signed images are involved. A problem that doesn't occur with MIT/BSD type licenses, like that for PostgreSQL.

---

<div class="post-metadata">

**Author:** ![Eskil\_Holum](https://avatars.discourse-cdn.com/v4/letter/e/cdc98d/32.png) [@Eskil\_Holum](https://forum.inductiveautomation.com/u/Eskil_Holum)\
**Post date:** [June 20, 2023, 12:31pm UTC](https://forum.inductiveautomation.com/t/why-no-mariadb-driver-with-docker-image/75261/3 "2023-06-20T12:31:57Z")

</div>

Ah, bummer, i tought the MariaDB was under the Apache 2.0 license? Luckily it was fairly easy to add it back myself.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 20, 2023, 12:35pm UTC](https://forum.inductiveautomation.com/t/why-no-mariadb-driver-with-docker-image/75261/4 "2023-06-20T12:35:10Z")

</div>

This is one of the reasons I lead with PostgreSQL, for anyone who asks.

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [June 20, 2023, 1:08pm UTC](https://forum.inductiveautomation.com/t/why-no-mariadb-driver-with-docker-image/75261/5 "2023-06-20T13:08:34Z")

</div>

Is restoring a gateway backup the only way to put the JDBC driver back in docker?

I'm a little fuzzy on how the file system stuff would work in that environment.

---

<div class="post-metadata">

**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\
**Post date:** [June 20, 2023, 1:10pm UTC](https://forum.inductiveautomation.com/t/why-no-mariadb-driver-with-docker-image/75261/6 "2023-06-20T13:10:15Z")

</div>

A GWBK file is just a zip file, rename it as such, unzip it, and upload the driver from inside the relevant folder back onto your running gateway.

---

<div class="post-metadata">

**Author:** ![Eskil\_Holum](https://avatars.discourse-cdn.com/v4/letter/e/cdc98d/32.png) [@Eskil\_Holum](https://forum.inductiveautomation.com/u/Eskil_Holum)\
**Post date:** [June 20, 2023, 1:27pm UTC](https://forum.inductiveautomation.com/t/why-no-mariadb-driver-with-docker-image/75261/7 "2023-06-20T13:27:17Z")

</div>

I didnt do it this way, i had the driver on another gateway and just retrieved the .jar file from the installation folder and copied the driver settings from the other gateway.

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [June 20, 2023, 2:01pm UTC](https://forum.inductiveautomation.com/t/why-no-mariadb-driver-with-docker-image/75261/8 "2023-06-20T14:01:55Z")

</div>

Just for clarity, the Docker image does ship with the MariaDB Connector/J JDBC driver (currently version 2.7.3).

 ![2023-06-20 at 8.48 AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/c/bc4fb591aaee0961f4dd034baf304505ca2c974b.png)

As already discussed, restoring a gateway backup applies the JDBC drivers preserved in the GWBK--this may be why you are seeing different JDBC driver sets available in your restored gateway container.
