MariaDB access for Docker containers

[spir0o]

Hi,
I'm having general issues connecting my docker containers to MariaDB 10 (installed through Synology packages center, version 10.3.21-0063).

For example, with the great tutorial from wwwampy, when I put the variables for database (LAN IP from NAS with port 3307), it fails to connect. I also tried with "localhost" / "127.0.01". I've already created the database and user with phpMyAdmin.

On the otherside, I was able to connect Nextcloud (webstation version) with LAN IP address and port to MariaDB 10.

I feel like I'm missing something. Would someone be nice enough to help a newbie ?

Thanks in advance et stay healthy

 

[Rusty]

LAN IP address and port to MariaDB 10

What port are you running Maria on? In some cases, Maria/mysql is running on 3306 and in some on 3307 port. So what port are you using with Nextcloud for example?

 

[spir0o]

Thank you for your answer.

For Nextcloud, I use port 3307
'dbname' => 'nextcloud2',
'dbhost' => '192.168.1.156:3307',

 

[Rusty]

Then I guess DB is broadcasting on port 3307 on your nas and docker containers should pick it up without any problem.

What container are you trying to run? Firefly?

If so, then make sure that the DB_HOST variable is configured not just with the ip address of the DB host (in your case that's your NAS IP) but also the port. So just like with dbhost parameter for nextcloud, use IP_ADDRESS: PORT as a value.

Also, Firefly can use 2 more variables if setting up a specific port as a variable is needed.

DB_CONNECTION	mysql
DB_PORT	port number

 

[spir0o]

I tried with IP:PORT with no success. I thought this was an easy fix but it doesn't seem so. So I resorted in creating a new MariaDB database with docker and connected through docker bridge. And now it works. My only fear is that i've seen that docker bridge IPs change when I restart the NAS.
Thank you for your help !

 

[Rusty]

My only fear is that i've seen that docker bridge IPs change when I restart the NAS.

It won't don't worry. Still bare metal Maria should work. Glad you got it sorted via docker alternative.

 

[3zzy]

Had the same issue, I resolved it by choosing "Host" for network instead of "Bridge". if you already have the container created, you have to delete and recreate again.

 

[one-eyed-king]

By default the MariaDB package only allows root access from localhost/127.0.0.1. This is why it works with mode=host and did not with mode=bridge. In mode=host the container shares the namepsace for the network device with the host (read: behaves network-wise exactl like the host). Btw: you can set and/or see the port in DSM's MariaDB configuration ui.

If you want to connect a container in the bridged network, you might want to read this link: Question - MariaDB 10 Error: 2006 MySQL server has gone away

 

[3zzy]

By default the MariaDB package only allows root access from localhost/127.0.0.1. This is why it works with mode=host and did not with mode=bridge. In mode=host the container shares the namepsace for the network device with the host (read: behaves network-wise exactl like the host). Btw: you can set and/or see the port in DSM's MariaDB configuration ui.

If you want to connect a container in the bridged network, you might want to read this link: Question - MariaDB 10 Error: 2006 MySQL server has gone away

Ah that makes sense. Thanks mate!

 

[one-eyed-king]

Welcome! ... and also welcome to the forum 3zzy!

 

[sircastor]

I registered and want to post this for the sake of anyone who might come along looking for answers like I was. I have been trying to set up Firefly III in a Docker container with the MariaDB package running on directly on DSM. Aside from the noted suggestions above, Docker was unable to access MariaDB because the default new user made in phpMyAdmin is just for localhost.

The idea came from this thread: MariaDB access for Docker containers

Anyway, I hope that helps anyone coming behind me.