How to establish Docker multi-container connection with Mysql+Tomcat
This article mainly introduces Docker multi-container connection (taking Tomcat+Mysql as an example). Docker provides a method for direct access by multiple containers, which allows multiple containers to directly access Access through network ports
Docker provides a method for direct access by multiple containers. The simplest way is to directly use the port mapping -p parameter to specify the mapped port or -P to map all ports. Multiple containers can directly access through network port for access.
But the network port mapping method is not the only way to connect multiple containers in Docker. A safer method is to use Docker's connection system (--link) to connect multiple containers. When the containers are connected together , the recipient container can see the information of the source container.
Take Tomcat + Mysql as an example to establish a connection between containers
To establish a connection directly between containers, use the --link option
--link
Here we create a Tomcat + Mysql service to illustrate how to establish a connection between two or more containers.
To establish a container connection, you must rely on the name of the container. Use --name to specify the name of the source container as mysql
docker run --name mysql -d gsoft/mysql:5.6
Next create the tomcat container and connect to the mysql container
The code is as follows:
docker run --name tomcat -d -p 80:8080 --link mysql:mysql gsoft/tomcat:7.0
The --link option specifies that the container to be connected is mysql.
Container intercommunication information
After establishing a connection between two containers, the receiving container (Recipient) will inevitably need to access the resources of the source container (Source). When we establish a connection for the container, the source container does not use -p/-P to specify the port to be exposed when it is created, so how to access the source container information?
In order to allow the receiving container to access the information of the source container, Docker provides two methods:
Environment Variables
/etc/hosts file
Environment variables
When Docker connects to the container, it will use --link The provided parameters automatically create some environment variables in the recipient container, including the environment variables set using the ENV command in the source container's Dockerfile and when the source container starts (docker run), use -e or - -env, the environment variable specified by the --env-file parameter.
Mainly includes the following environment variables, assuming alias=mysql.
<alias>_PORT <alias>_PORT_<port>_<protocol> <alias>_PORT_<port>_<protocol>_ADDR <alias>_PORT_<port>_<protocol>_PORT <alias>_PORT_<port>_<protocol>_PROTO <alias>_NAME
For example:
#docker run -i -t --rm --link mysql:mysql ubuntu:14.04 env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOSTNAME=9c74aa611463 TERM=xterm MYSQL_PORT=tcp://172.17.0.3:3306 MYSQL_PORT_3306_TCP=tcp://172.17.0.3:3306 MYSQL_PORT_3306_TCP_ADDR=172.17.0.3 MYSQL_PORT_3306_TCP_PORT=3306 MYSQL_PORT_3306_TCP_PROTO=tcp MYSQL_NAME=/desperate_ritchie/mysql HOME=/root
In the above example, the container alias is specified as msyql, so all environment variables start with MYSQL_.
Note that if the source container is restarted, the environment variable information in the receiving container will not be automatically updated. Therefore, if you want to use the IP address of the source container, please use /etc/ Host information configured in hosts.
/etc/hosts file
In addition to environment variables, Docker also updates the hosts information in the /etc/hosts file of the receiving container.
# docker run -i -t --rm --link mysql:mysql ubuntu:14.04 /bin/bash # cat /etc/hosts 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters 172.17.0.3 mysql 115346bdb403 172.17.0.5 09bdf7805133
As can be seen from the above, two additional pieces of information are added to the hosts file of the receiving container, the local IP and alias and the IP and alias of the source container (mysql).
Different from environment variables, if the source container is restarted, the information in /etc/hosts in the receiving container will be automatically updated.
The above is the detailed content of How to establish Docker multi-container connection with Mysql+Tomcat. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The steps to update a Docker image are as follows: Pull the latest image tag New image Delete the old image for a specific tag (optional) Restart the container (if needed)

How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

Steps to create a Docker image: Write a Dockerfile that contains the build instructions. Build the image in the terminal, using the docker build command. Tag the image and assign names and tags using the docker tag command.

Four ways to exit Docker container: Use Ctrl D in the container terminal Enter exit command in the container terminal Use docker stop <container_name> Command Use docker kill <container_name> command in the host terminal (force exit)

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

To save the image in Docker, you can use the docker commit command to create a new image, containing the current state of the specified container, syntax: docker commit [Options] Container ID Image name. To save the image to the repository, you can use the docker push command, syntax: docker push image name [: tag]. To import saved images, you can use the docker pull command, syntax: docker pull image name [: tag].

You can query the Docker container name by following the steps: List all containers (docker ps). Filter the container list (using the grep command). Gets the container name (located in the "NAMES" column).

Methods for copying files to external hosts in Docker: Use the docker cp command: Execute docker cp [Options] <Container Path> <Host Path>. Using data volumes: Create a directory on the host, and use the -v parameter to mount the directory into the container when creating the container to achieve bidirectional file synchronization.
