Why Docker Is Not Suitable for Running MySQL: Data Security, Performance, State, and Resource Isolation Issues

Everyone, I am a top architect. When people ask about environment setup and deployment, I always ask whether they are learning or deploying online.

For learning, Docker can quickly install MySQL with a single command, and the container can be removed cleanly after use. However, this advice only applies to personal learning; production deployments require a thorough assessment of whether the service is suitable for containerization.

Data Security Issues

Do not store data inside containers because containers can be stopped or removed at any time, leading to data loss. Use volume mounts for persistence, but Docker volumes are built on Union FS and do not guarantee data safety; crashes can corrupt databases, and shared volumes may stress the host hardware.

Performance Issues

MySQL, as a relational database, has high I/O demands. Running multiple MySQL instances on a single physical machine can cause I/O bottlenecks and significantly degrade read/write performance.

During a Docker challenges session, an architect from a state-owned bank noted that database performance bottlenecks usually appear at the I/O layer, and Docker’s approach of stacking many containers can exacerbate storage I/O pressure.

Possible mitigation strategies include:

1) Separate database program from data – store data on shared storage while keeping the program in the container, allowing automatic recreation of containers on failure.

2) Use lightweight or distributed databases – Docker is designed for stateless services that can be restarted automatically.

3) Properly place high‑I/O workloads – deploy databases on physical machines or KVM; examples include Tencent Cloud TDSQL and Alibaba OceanBase.

State Issues

Docker’s horizontal scaling is intended for stateless services, not for databases that maintain state.

When a database runs in Docker, storage services must be provided separately; otherwise, stateful data may be lost.

Resource Isolation

Docker’s resource isolation via cgroups limits maximum consumption but cannot fully isolate resources from other processes; heavy usage by other applications can degrade MySQL performance.

Higher isolation levels increase overhead, and while Docker excels at horizontal scaling for stateless services, databases do not fit this model.

Can MySQL Run in Containers?

MySQL can be containerized in certain scenarios:

1) Workloads tolerant of data loss (e.g., user search) can use sharding to increase throughput.

2) Docker suits lightweight or distributed databases; if a container fails, a new one can be started automatically.

3) With middleware and orchestration, containers can provide auto‑scaling, disaster recovery, and multi‑node capabilities.

Examples include Tongcheng Travel, JD.com, and Alibaba’s containerized databases.

Feel free to discuss and share your views; you can also contact me for further communication.

--- Promotion ---

We have created an AI Club community to explore ChatGPT and the new AI era. Members receive a permanent ChatGPT account, tutorials, and various side‑project resources.

Benefits include:

Regular sharing of ChatGPT usage methods, latest news, and business value.

Discussion of AI opportunities and collaborative growth.

One‑year after‑sales service for side‑project development.

The second phase of the community is priced at 399 CNY, now discounted to 159 CNY with early‑bird coupons.

Join now to receive valuable resources far exceeding the entry fee.