OSX Docker / WordPress / MySQL —连接错误：（1130）不允许主机“ xxx.xxx.xxx.xxx”连接到此MariaDB服务器

Question

This question is different than other similar questions because it involves running in a Docker container on OS X , which has previously been running fine for a week, and is now failing.

Following the instructions here:

https://medium.com/@tatemz/local-wordpress-development-with-docker-3-easy-steps-a7c375366b9

I was able to get a local WordPress install up and running very quickly and it's been wonderful.

Today when I start it up, there is a connection refusal that looks like it would be very simple to address if I could figure out two things from the following error messages:

MySQL Connection Error: (1130) Host '172.19.0.3' is not allowed to connect to this MariaDB server
Warning: mysqli::mysqli(): (HY000/1130): Host '172.19.0.3' is not allowed to connect to this MariaDB server in - on line 22

The 2 things I need to figure out are:

1. "line 22" in what file? Is this a config file? What is the file name?
2. On a Mac/Docker deployment like this, what is the path to this file?

The docker container directory only contains a WordPress install directory. There doesn't appear to be anything related to MySQL/MariaDB in that directory. I've read through a lot of documentation on Mac deployments of MySQL and where the config files would live, but being in a Docker container this is a different beast. The documentation I have found does not apply.

I have looked into SSH'ing into a Docker container (I'm a baby at Docker) but I don't even know if that's a thing you do.

Answer 1

Your issue is probably with the MySQL container starting before the WordPress container. Try adding the depends_on tag to your docker-compose.yml file and remove the links tag. You also want to add restart: always to both containers.

  my-wp:
    image: wordpress
    volumes:
      - ./:/var/www/html
    depends_on:
      - my-wpdb
    restart: always
    ports:
      - "8080:80"
    environment:
      WORDPRESS_DB_PASSWORD: ChangeMeIfYouWant

You can take a look at your error logs by running:

docker logs -f CONTAINERNAME >/dev/null

If you want to open up a shell inside your container, you can run:

docker exec -ti CONTAINERNAME /bin/bash