Hi Furkan,
Each database has a superuser name and password, for creating the workarea
and the dbuser that will be active during operation. So all of these are
needed.
As for why mysql.hostname, mysql.server, and mysql.client are needed --
each database driver has specific needs. There is no
Hi Karl,
I've found why it didn't work. I thought that these are enough:
However, these key/value pairs are read by ManifoldCF too:
So, I've added that properties to make it work. Shouldn't hostname,
dbsuperusername and dbsuperuserpassword be enough?
Kind Regards,
Furkan
Hi Karl,
When I try to connect a dockerized MySQL from host machine I use ip
address. Symbolic names can be used inter-docker connections with linked
containers.
I've tried all combinations and none of them worked. I couldn't figure out
the reason why ManifoldCF does not use parameters defined
Hi Furkan,
This gives me pause:
A virtualized environment may require use of symbolic names rather than
hard IP addresses.
Karl
On Sat, Nov 24, 2018 at 7:53 AM Furkan KAMACI
wrote:
> Hi Karl,
>
> Same config with same MySQL version in non-docker environment works. I can
> successfully
Hi Karl,
Same config with same MySQL version in non-docker environment works. I can
successfully connect to mysql docker via:
mysql -h 172.17.0.2 -u root -p
Here is my config for MySQL:
I've put some logging into ConnectionFactory and this is what I get:
--
Hi All,
I try to test ManifoldCF via docker. I've run mysql as follows:
docker run --name custom-mysql -v /home/ubuntu/mysql-conf:/etc/mysql/conf.d
-e MYSQL_ROOT_PASSWORD=mypass -d mysql:5.7.16
I've run my docker container of ManifoldCF as follows:
docker run --name manifoldcf --link
