PHP application can't connect to MariaDB using Docker Compose

Question

My application is set up using Docker Compose. My docker-compose.yml contents;

version: "3.1"
services:
  nginx-proxy:
    image: jwilder/nginx-proxy
    container_name: nginx-proxy
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
  db:
    image: mariadb:10.4
    restart: always
    ports:
      - "3307:3306"
    volumes:
      - ./mysql:/var/lib/mysql
    container_name: mariadb
    environment:
      - MYSQL_DATABASE=dbname
      - MYSQL_PASSWORD=dbpass
      - MYSQL_RANDOM_ROOT_PASSWORD=yes
      - MYSQL_USER=dbuser
  phpapp:
    depends_on:
      - nginx-proxy
      - db
    image: myhub/myrepo
    restart: always
    container_name: phpapp
    expose:
      - 80
      - 443
    environment:
      - APP_ENV=prod
      - APP_SECRET="secret"
      - CORS_ALLOW_ORIGIN="^.*?$$"
      - DATABASE_URL="mysql://dbuser:dbpass@db/dbname"
      - VIRTUAL_HOST=phpapp.com
networks:
  default:
    external:
      name: nginx-proxy

However, when I try to connect to the database in the application I get an error message; SQLSTATE[HY000] [2002] No such file or directory.

I can, however, connect on port 3307 on my localhost with the correct username and password. Also, when I access the container using docker exec -ti phpapp /bin/bash and run env I get all the environment variables listed and they are correct.

When I execute docker network inspect nginx-proxy I get;

[
  {
    "Name": "nginx-proxy",
    "Id": "2529933d7e38cfba34e0e876e43a96fc4c8d7321c1e89048319ba804b00e1026",
    "Created": "2018-12-12T05:04:01.9044879Z",
    "Scope": "local",
    "Driver": "bridge",
    "EnableIPv6": false,
    "IPAM": {
      "Driver": "default",
      "Options": {},
      "Config": [
      {
        "Subnet": "172.18.0.0/16",
        "Gateway": "172.18.0.1"
      }
      ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
      "Network": ""
    },
    "ConfigOnly": false,
    "Containers": {},
    "Options": {},
    "Labels": {}
  }
]

The containers array is empty, however a default (external) network is set in the docker-compose.yml.

What port does your php app use to connect to the db? 3306? Make sure that your containers are really in the same docker network: "docker network inspect nginx-proxy" — Hannes
– Hannes, Commented Dec 12, 2018 at 8:06
I've updated my question with the result for that command, thank you. — user10779576
– user10779576, Commented Dec 12, 2018 at 9:41

Emircan Ok · Accepted Answer · 2018-12-12 08:25:23Z

2

Welcome to stackoverflow :)

I think maybe it is not working for db container not linked from phpapp container. Can you try like this?

version: "3.1"
services:
  nginx-proxy:
    image: jwilder/nginx-proxy
    container_name: nginx-proxy
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
  db:
    image: mariadb:10.4
    restart: always
    ports:
      - "3307:3306"
    volumes:
      - ./mysql:/var/lib/mysql
    container_name: mariadb
    environment:
      - MYSQL_DATABASE=dbname
      - MYSQL_PASSWORD=dbpass
      - MYSQL_RANDOM_ROOT_PASSWORD=yes
      - MYSQL_USER=dbuser
  phpapp:
    depends_on:
      - nginx-proxy
    links:
      - db
    image: myhub/myrepo
    restart: always
    container_name: phpapp
    expose:
      - 80
      - 443
    environment:
      - APP_ENV=prod
      - APP_SECRET="secret"
      - CORS_ALLOW_ORIGIN="^.*?$$"
      - DATABASE_URL="mysql://dbuser:dbpass@db/dbname"
      - VIRTUAL_HOST=phpapp.com
networks:
  default:
    external:
      name: nginx-proxy

I moved db from depends_on to links. You must use db for hostname in database connection now.

I hope i could help.

answered Dec 12, 2018 at 8:25

Emircan Ok

3572 silver badges14 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Sven Hakvoort Over a year ago

Please note that links does not work in version 3, therefore it will not work in the case of the OP and will eventually be deprecated, see: docs.docker.com/network/links

vivekyad4v Over a year ago

Also, I guess in compose services can reach out to each other by using their names itself. No need to provide links option.

user10779576 Over a year ago

Thank you and thanks for your suggested solution. However, like Sven and vivekyad4v pointed out; version 3 supports using the name of a container to link services.

user10779576 · Accepted Answer · 2018-12-12 11:10:54Z

0

Well, I've found the solution to this problem. However, it's not the one I expected. The database URL is defined as:

DATABASE_URL="mysql://dbuser:dbpass@db/dbname"

It should be without quotes, like this:

DATABASE_URL=mysql://dbuser:dbpass@db/dbname

Now everything seems to work, does anyone know when and why you can and can't use quotes?

answered Dec 12, 2018 at 11:10

user10779576

314 bronze badges

Collectives™ on Stack Overflow

PHP application can't connect to MariaDB using Docker Compose

2 Answers 2

3 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related