January-7th-2020, 08:46 AM
I read this article https://mariadb.com/kb/en/configuring-ma...nt-access/ carefully.
I understood that mariadb server supports client access from remote stations once it is enabled. I read that the default port in use is port 3306.
So if you want your PC to access the netPI mariadb container over TCP/IP then you have to "open" the port 3306 in the container. This is done using the "port mapping" feature used while a containe is started. It is the same like the port 22 to enable the console connection, but now for port 3306 for mariadb access from remote.
Since you are new to docker: port mapping can only be setup during the first container start. It is never ever possible to "open" other ports while a container is running. So all applications that will run in future in a container and their used ports need to be known from the beginning and handed over to Docker container start parameter.
I understood that mariadb server supports client access from remote stations once it is enabled. I read that the default port in use is port 3306.
So if you want your PC to access the netPI mariadb container over TCP/IP then you have to "open" the port 3306 in the container. This is done using the "port mapping" feature used while a containe is started. It is the same like the port 22 to enable the console connection, but now for port 3306 for mariadb access from remote.
Since you are new to docker: port mapping can only be setup during the first container start. It is never ever possible to "open" other ports while a container is running. So all applications that will run in future in a container and their used ports need to be known from the beginning and handed over to Docker container start parameter.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
