Why Running MySQL in Docker Can Be Risky: 5 Critical Issues

Container definition: a container solves the problem of ensuring software runs correctly when switching execution environments.

Containers and Docker are currently hot topics, and a heated debate exists on whether MySQL should be containerized.

Data Security Issues

Data should not be stored inside containers because containers can be stopped or removed, causing data loss. Users should use volume mounts to persist data outside the container.

Performance Issues

MySQL is an I/O‑intensive relational database; running multiple instances on a single host can create I/O bottlenecks and significantly degrade read/write performance.

Strategies to mitigate performance problems include:

1) Separate database program and data

Store data on shared storage while keeping the database program in the container, and avoid placing data on the host to reduce impact on the host machine.

2) Use lightweight or distributed databases

Deploy lightweight or distributed databases in Docker so that if a container fails, a new one can be started automatically.

3) Proper application placement

For high‑I/O workloads, deploy the database on physical machines or KVM rather than in containers; services like Tencent Cloud TDSQL and Alibaba Cloud OceanBase run on physical servers.

State Issues

Docker’s horizontal scaling is designed for stateless services and is unsuitable for databases that maintain state; storage services must be provided separately.

Resource Isolation

Docker uses cgroups for resource limits, which can restrict maximum usage but cannot fully isolate resources from other processes; excessive resource consumption by other applications can affect MySQL’s performance.

Can MySQL Run in Containers?

MySQL is not completely unsuitable for containers. It can be containerized for workloads insensitive to data loss, for sharded databases that increase throughput, for lightweight or distributed databases that benefit from automatic restart, and when using middleware that provides auto‑scaling, disaster recovery, and multi‑node capabilities. Notable examples include containerized databases used by companies such as Tongcheng Travel, JD.com, and Alibaba.