Docker ERROR 2002 (HY000): Can't connect to MySQL server on 'db' (115)

Docker ERROR 2002 (HY000): Can't connect to MySQL server on 'db' (115)

July 14, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Docker ERROR 2002 (HY000): Can't connect to MySQL server on 'db' (115)

Solving Docker MySQL Connection Errors: A Comprehensive Guide

As an experienced developer working with Docker containers for Magento deployment, I’ve encountered common issues like the “Can’t connect to MySQL server on ‘db’ (115)” error. This post will guide you through understanding this problem and provide a step-by-step solution using a real-world example from Mark Shust’s Magento Docker configuration repository.

Understanding the “Can’t connect to MySQL server on ‘db’ (115)” Error

This error typically occurs when your application can’t establish a connection with the MySQL container running inside the Docker network. The error message suggests that the system couldn’t reach the specified host ‘db’ at port 3306.

Analyzing Your Environment and Configuration

You mentioned you’re using Mark Shust’s Magento Docker configuration. Let’s break down your provided YAML file for better understanding:

version: "3"

services:
  db:
    image: mariadb:10.1
    command: mysqld --innodb_force_recovery=6 --lower_case_table_names=1 --skip-ssl --character_set_server=utf8mb4 --explicit_defaults_for_timestamp
    ports:
      - "3306:3306"
    env_file: env/db.env
    volumes:
      - dbdata:/var/lib/mysql

The db service is defined with the MySQL image and exposed on port 3306. The configuration file env/db.env contains your database environment variables.

Troubleshooting Steps to Resolve the Issue

Step 1: Verify Your Network Configuration

Ensure that all services are running within the same Docker network. By default, they should be part of the same bridge network created by Docker when you run your containers for the first time.

You can check this using:

docker network inspect bridge --format='{{(index .IPAM.Config 0).Gateway}}'

Replace bridge with the name of your custom network if applicable.

Step 2: Check Your Environment Variables

The MySQL container requires appropriate environment variables to connect correctly. The env/db.env file should contain variables like:

MYSQL_ROOT_PASSWORD=your_root_password
MYSQL_DATABASE=magneto_magento
MYSQL_USER=magneto_magento
MYSQL_PASSWORD=magento_magento

Ensure these values are correct and accessible to the container.

Step 3: Verify Container Status

Check if your containers are running correctly:

docker ps

Look for any errors or status messages that might indicate a problem with the db service.

For more advanced troubleshooting techniques, I recommend exploring our Laravel Company blog, where we cover best practices for Docker deployment and common issues faced by developers.

Check out these related articles:

Conclusion

Resolving the “Can’t connect to MySQL server on ‘db’ (115)” error requires a systematic approach. By verifying your network configuration, checking environment variables, and inspecting container status, you can often identify and fix the issue.

Remember that Docker requires careful configuration of networks, volumes, and environment variables for seamless communication between containers. Always consult official documentation and trusted resources like the Laravel Company blog for expert guidance on Docker deployment strategies.

Happy coding!

Database Configuration Deployment Errors

Our network