Skip to main content

Connect MySQL Docker Container using Work Bench | SQL Yog | Docker Host Netwrork

Connect MySQL Docker container using Work Bench | SQL Yog and Other tool:

To connect MySQL Docker container using Workbench OR SQLyog require to run MySQL Docker container with Host Network, and detached (in the background)mode.
Explore more about Docker detached mode - https://severalnines.com/database-blog/mysql-docker-containers-understanding-basics

Following example run MySQL Docker container in detached mode, mounting volume - /mysql/mysql_data_1/data_1 outside contanier, with name - mysql_1, and MySQL server 8.0.18 

#docker run -d --network host \
--volume=/mysql/mysql_2/data_1:/var/lib/mysql \
--name=mysql_1 mysql/mysql-server:8.0.18

But it has limitations:

  • You can have only one host network per machine host, means you can not create more.
  • You can't link other container using --link
  • Port mapping is not supported, means you can access MySQL at port 3306 only
Explore more about Docker Host Network:

Get MySQL root password:
# docker logs mysql_2 2>&1 | grep GENERATED
[Entrypoint] GENERATED ROOT PASSWORD: sIm7IPUmvUSODaKocvALYRiv6@S

Set New password for MySQL user root:
#docker exec -it mysql_1 mysql -uroot -p
mysql> alter user 'root'@'localhost' identified by 'new_password';

Access bash for MySQL Docker container:
#docker exec -it mysql_2 bash

Install text editor vi to change default authentication: 
#yum install vi

Inspect MySQL Docker Container:
You will be able to see HostConfig, NetworkMode, Mounts, PortBindings and other items
#docker inspect mysql_1 | more

Ref.:
https://docs.docker.com/network/network-tutorial-host/

Explore:

Docker Network
7 layers (level) of OSI
Docker v/s Kubernetes
Weave v/s Calico
Weave
VXLAN
What is VXLAN
VXLAN White papers





Comments

  1. Connecting a MySQL Docker container using Workbench or SQL Yog is a game changer for database management! Discover the best practices with AmbitionHost to streamline your workflow.

    ReplyDelete

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...

MySQL slave Error_code: 1032 | MySQL slave drift | HA_ERR_KEY_NOT_FOUND

MySQL slave Error_code: 1032 | MySQL slave drift: With several MySQL, instance with master slave replication, I have one analytics MySQL, environment which is larger in terabytes, compared to other MySQL instances in the environment. Other MySQL instances with terabytes of data are running fine master, slave replication. But this analytics environment get started generating slave Error_code :1032. mysql> show slave status; Near relay log: Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_log_pos 5255306 Near master section: Could not execute Update_rows event on table <db_name>.<table_name>; Can't find record in '<table_name>', Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_l...

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...