How can I automatically import a SQL database into my PHP Docker container?

I've did it, thanks for your answers! This is the complete docker-compose.yml file. I've used /docker-entrypoint-initdb.d/ directory where I placed the database to be imported.

YAMLCopied
services:
  app:
    build:
      context: .
      dockerfile: Dockerfile
    image: my-laravel-app
    container_name: my-laravel-app
    restart: unless-stopped
    working_dir: /var/www
    volumes:
      - ./:/var/www
      - ./.env:/var/www/.env
    environment:
      - APP_ENV=local
    networks:
      - app-network

  nginx:
    image: nginx:alpine
    container_name: my-nginx
    ports:
      - "8000:80"
      - "${VITE_PORT:-5173}:${VITE_PORT:-5173}"
    volumes:
      - ./:/var/www
      - ./nginx.conf:/etc/nginx/conf.d/default.conf:ro
      - ./docker/php/local.ini:/usr/local/etc/php/conf.d/local.ini
    depends_on:
      - app
    networks:
      - app-network        

  node:
    platform: linux/arm64/v8
    build:
      context: .
      dockerfile: Dockerfile.node
    image: my-laravel-node
    container_name: my-laravel-node
    ports:
      - "3000:3000"
    restart: unless-stopped
    working_dir: /var/www
    volumes:
      - ./:/var/www
      - /var/www/node_modules
    networks:
      - app-network

  db:
    platform: linux/x86_64
    image: mysql:8.0
    container_name: my-mysql
    restart: unless-stopped
    environment:
      MYSQL_DATABASE: ${DB_DATABASE}
      MYSQL_ROOT_PASSWORD: ${DB_PASSWORD}
      MYSQL_PASSWORD: ${DB_PASSWORD}
      MYSQL_USER: ${DB_USERNAME}
    volumes:
      - dbdata:/var/lib/mysql
      - ./data.sql:/docker-entrypoint-initdb.d/data-dump.sql  
    networks:
      - app-network
    ports:
      - "3306:3306"

networks:
  app-network:
    driver: bridge

volumes:
  dbdata:
    driver: local

It is simple. Your database do not run in this application container. Rather, it is probably running in a different container (i.e. hostname db in your environment).

When your image is building, it has no access to other running container(s).

So instead of using RUN to do things in build time, you should probably have script in your container to run the import when you first run the image against your environment, which provides proper access to the database.

This is a problem with the RUN directive, more specifically the command in it:

BASHCopied
RUN wait-for-it -t 30 ${DB_HOST}:${DB_PORT} \
if [ -f /var/www/database/bsp.sql ]; then \
    mysql -u ${DB_USERNAME} -p${DB_PASSWORD} -h ${DB_HOST} ${DB_DATABASE} < /var/www/database/bsp.sql; \
fi

What we can see is, that these compound commands do result in exit code 2.

This is a hint that it is a syntax error, because in the first line the wait-for-it command is not separated from the if that follows.

Insert a semicolon "";"" and additionally set the sh(1) shell options to errexit (-e) and xtrace (-x) to have it more straight forward:

BASHCopied
RUN set -ex; \
    wait-for-it -t 30 ${DB_HOST}:${DB_PORT}; \
    if [ -f /var/www/database/bsp.sql ]; then \
        mysql -u ${DB_USERNAME} -p${DB_PASSWORD} -h ${DB_HOST} ${DB_DATABASE} < /var/www/database/bsp.sql; \
    fi

Additionally look into the build log for messages like

sh: syntax error near unexpected token `then'

or similar.

There are some other sloppy things in the Dockerfile, double check also the COPY lines, it looks like you are copying two times the same files. Before adding new functionality into the build, clean up first and commit the files to version control. Then it's easier to throw things around with Dockerfiles.