Laravel Docker DB Issue

services:
app:
build:
context: .
dockerfile: Dockerfile
container_name: laravel_app
volumes:
– ./shareyourthoughts:/var/www/html
networks:
– laravel_network
depends_on:
– db
ports:
– "8080:80" # Change this to the desired host port

db:
image: mysql:8.0
container_name: laravel_db
restart: always
environment:
MYSQL_DATABASE: laravel
MYSQL_USER: laravel
MYSQL_PASSWORD: password
MYSQL_ROOT_PASSWORD: rootpassword
volumes:
– db_data:/var/lib/mysql
networks:
– laravel_network

adminer:
image: adminer
container_name: adminer
restart: always
ports:
– "8081:8080" # Change this to the desired host port for Adminer
networks:
– laravel_network

networks:
laravel_network:
driver: bridge

volumes:
db_data:
db host: db unknow when run php artisan migrate

### 1. Check Database Configuration in `.env`
Make sure your database configuration in the `.env` file of your Laravel application is set correctly. The `DB_HOST` should match the service name defined in your `docker-compose.yml`, which in this case is `db`. Your `.env` file should have something like this:

DB_CONNECTION=mysql
DB_HOST=db
DB_PORT=3306
DB_DATABASE=laravel
DB_USERNAME=laravel
DB_PASSWORD=password

### 2. Run Docker Compose Up
When running your Docker containers, make sure to use the `docker-compose up` command (preferably with the `–build` flag the first time to ensure everything is built properly):

docker-compose up --build

### 3. Wait for Database Initialization
Sometimes, the Laravel application starts before the MySQL database is fully ready to accept connections. You can use a simple wait-for-it script to handle this. Here's how to implement it:

1. Create a file named `wait-for-it.sh` in your project root (you can find it [here](https://github.com/vishnubob/wait-for-it)) and make it executable:

chmod +x wait-for-it.sh

2. Modify your `Dockerfile` to copy the script into the container and adjust your `CMD` command to use it:

FROM php:8.3-apache

    # Copy wait-for-it script
    COPY wait-for-it.sh /usr/local/bin/wait-for-it

    # Set the working directory
    WORKDIR /var/www/html

    # Copy the rest of your application files
    COPY . .

    # Install any PHP extensions if needed

    # Run the application using the wait-for-it script
    CMD ["wait-for-it", "db:3306", "--", "php", "artisan", "serve", "--host=0.0.0.0"]

### 4. Check Docker Network
Ensure all services are in the same network. You have correctly set them up in your `docker-compose.yml`, but double-check by running:

docker network inspect laravel_network

This command will show you all the containers connected to that network.

### 5. Logs and Error Messages
Check the logs for both the Laravel application and the MySQL database to see if there are any specific error messages that could give you more information:

docker-compose logs app
docker-compose logs db

### 6. Rebuild and Restart
If you make any changes to your `.env` or `docker-compose.yml`, don’t forget to rebuild and restart your containers:

docker-compose down
docker-compose up --build

By following these steps, you should be able to resolve the "unknown database host" issue when running migrations in your Laravel application within Docker. Let me know if you need further assistance!