March-27th-2019, 06:51 PM
Hey Armin,
thanks for your fast reply.
I've tested the mysql-server in another container where it didn't work either, so the network settings were not the cause, sorry.
I have tried hard, but I just could not manage to get connections from outside to the mysql-server running on debian. On alpine linux it somehow works well. Since the drivers for the networks interface are debian-packages, I cannot integrate them in my alpine-linux-mysql container.
Since in Docker every task should run in its own container, wouldn't it be more straight forward to let the driver run in one container and the database in another container and somehow forward the incoming connections from the "network-container" to the "mysql-container"? Do you think this would work? And if so, do you have an idea what I would need to change?
Best regards,
Andi
thanks for your fast reply.
I've tested the mysql-server in another container where it didn't work either, so the network settings were not the cause, sorry.
I have tried hard, but I just could not manage to get connections from outside to the mysql-server running on debian. On alpine linux it somehow works well. Since the drivers for the networks interface are debian-packages, I cannot integrate them in my alpine-linux-mysql container.
Since in Docker every task should run in its own container, wouldn't it be more straight forward to let the driver run in one container and the database in another container and somehow forward the incoming connections from the "network-container" to the "mysql-container"? Do you think this would work? And if so, do you have an idea what I would need to change?
Best regards,
Andi