同一Docker容器内Python无法连接MySQL数据库求助

Hey there! Let's work through this MySQL connection error together—even though you’ve got MySQL up and running, there are a few common pitfalls when running both your Python app and database in the same Docker container. Let’s break down the fixes step by step:

1. First, confirm MySQL is actually listening locally in the container #

Sometimes even if MySQL shows as "started", it might not be accepting connections on 127.0.0.1:3306. Let’s verify:

• Jump into your running container’s shell:

  docker exec -it <your-container-name-or-id> bash
  

• Once inside, check if the MySQL process is running:

  ps aux | grep mysqld
  

  You should see a mysqld process listed here. If not, restart MySQL with service mysql restart.
• Next, test a direct local connection to MySQL:

  mysql -h 127.0.0.1 -u <your-db-username> -p
  

  If this fails too, check your MySQL config file (usually at /etc/mysql/mysql.conf.d/mysqld.cnf or /etc/my.cnf) for the bind-address setting. It should be set to 127.0.0.1 (or 0.0.0.0 if you want broader access, but 127.0.0.1 is fine for same-container connections). Update the setting and restart MySQL if needed.

2. Fix the startup order problem #

This is super common when running multiple services in one container: your Python app might be launching before MySQL is fully ready to accept connections. Even if you start MySQL first, it takes a few seconds to initialize databases and start listening.

Add a wait script to your container’s startup process (either in your Dockerfile or entrypoint script) to ensure MySQL is ready before your app starts:

# Wait until MySQL responds to a connection
until mysql -h 127.0.0.1 -u <your-db-username> -p<your-db-password> -e "SELECT 1"; do
  echo "Waiting for MySQL to finish starting up..."
  sleep 2
done

# Now start your Python app
python your-app.py

This loop will keep checking until MySQL is reachable, then launch your app.

3. Double-check your connection code details #

It’s easy to overlook a typo here! Make sure your Python code uses the correct username, password, database name, and that the host is set to 127.0.0.1 (sometimes localhost can have weird behavior in containers, so 127.0.0.1 is more reliable). Here’s a sample correct connection snippet:

import mysql.connector

try:
    db_connection = mysql.connector.connect(
        host="127.0.0.1",
        user="your-db-user",
        password="your-db-pass",
        database="your-db-name"
    )
    print("Connected to MySQL successfully!")
except mysql.connector.Error as err:
    print(f"Error: {err}")

4. Verify your SQL backup was restored correctly #

Since you mentioned a .sql backup file, make sure it’s been imported into MySQL properly before your app tries to access it. Run this in the container’s shell to confirm:

mysql -u <your-db-username> -p<your-db-password> <your-db-name> < /path/to/your/backup.sql

Then log into the MySQL shell and check if your tables exist:

mysql -u <your-db-username> -p<your-db-name>
# Once inside:
SHOW TABLES;

If your tables don’t show up, the backup import failed—double-check the file path and backup content.

A quick best practice note #

While running both services in one container works for testing, for production setups, it’s better to use separate containers for your Python app and MySQL (linked via a Docker network). This makes scaling, maintenance, and debugging way easier—but that’s a topic for another time!

内容的提问来源于stack exchange，提问作者GuyIncognito23