flags: qr rd ra QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 >HEADER<<- opcode: QUERY, status: NOERROR, id: 32162

In the following steps, you’ll create the network first and then attach the MySQL container at startup.

Connect an already running container to a network.

Assign the network when starting the container.

There are two ways to put a container on a network: If you place the two containers on the same network, they can talk to each other. So, how do you allow one container to talk to another? The answer is Remember that containers, by default, run in isolation and don’t know anything about other processes So, like the following diagram, it’s best to run your app in multiple containers.

Running multiple processes will require a process manager (the container only starts one process), which adds complexity to container startup/shutdown.Īnd there are more reasons.

You don’t want to ship your database engine with your app then.

While you may use a container for the database locally, you may want to use a managed serviceįor the database in production.

Separate containers let you version and update versions in isolation.

There’s a good chance you’d have to scale APIs and front-ends differently than databases.The following are a few reasons to run the container separately: The following question often arises - “Where will MySQL run? Install it in the sameĬontainer or run it separately?” In general, each container should do one thing and do it well. But, now you will add MySQL to theĪpplication stack. Up to this point, you’ve been working with single container apps.

Create todo