Docker Laravel Access 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
– ./init-scripts:/docker-entrypoint-initdb.d
networks:
– laravel_network

phpmyadmin:
image: phpmyadmin/phpmyadmin:latest
container_name: phpmyadmin
restart: always # Add this line
environment:
PMA_HOST: db
PMA_USER: laravel
PMA_PASSWORD: password
PMA_PORT: 3306
ports:
– "8082:80"
depends_on:
– db

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

node:
image: node:latest
container_name: node
working_dir: /var/www/html # Set working directory to the root of your Laravel app
volumes:
– ./shareyourthoughts:/var/www/html # Mount the entire Laravel project
command: ["tail", "-f", "/dev/null"] # Keep the container running
networks:
– laravel_network

networks:
laravel_network:
driver: bridge

volumes:
db_data:
localhost:8080
forbidden

1. **Docker Service Status**:
Ensure that all Docker containers are running without errors. You can check the status of your services using:

docker-compose ps

2. **Network Configuration**:
Make sure that your Docker containers are properly connected to the `laravel_network`. You can verify this by inspecting the network:

docker network inspect laravel_network

3. **Permissions on Project Directory**:
The permissions on your `./shareyourthoughts` directory may cause issues. Ensure that the Docker daemon has the necessary permissions to read and write to this directory.

4. **Correct Port Mapping**:
Confirm that port `8080` is not already in use by another service on your host machine. You can check for running services on that port using:

netstat -tuln | find "8080"

5. **Accessing the App**:
After starting your containers, try accessing the application using `http://localhost:8080`. If you're using a specific web server configuration or if you're running any firewall, ensure that they allow traffic through that port.

6. **Logs for Errors**:
Check the logs of your app container to see if there are any error messages that can help identify the issue:

docker-compose logs app

7. **Firewall Settings**:
Make sure your firewall settings on Windows allow inbound traffic on port `8080`.

If you've gone through these steps and the issue persists, please provide any error messages from your logs, and I'll help you troubleshoot further!

# Install PHP extensions and enable necessary Apache modules
RUN apt-get update && apt-get install -y
libpng-dev
libjpeg-dev
libfreetype6-dev
&& docker-php-ext-configure gd –with-freetype –with-jpeg
&& docker-php-ext-install gd pdo pdo_mysql
&& a2enmod rewrite

# Install Composer
COPY –from=composer:latest /usr/bin/composer /usr/bin/composer
# Set the working directory
WORKDIR /var/www/html

# Copy existing application directory permissions
COPY –chown=www-data:www-data shareyourthoughts/ /var/www/html

# Set permissions for storage and cache
RUN chown -R www-data:www-data /var/www/html/storage /var/www/html/bootstrap/cache
&& chmod -R 775 /var/www/html/storage /var/www/html/bootstrap/cache

# Copy custom Apache configuration if needed
COPY ./apache/vhost.conf /etc/apache2/sites-available/000-default.conf

# Copy custom php.ini
COPY ./php-config/php.ini /usr/local/etc/php/
# Set permissions for logs
RUN mkdir -p /var/log && touch /var/log/php_errors.log && chmod 777 /var/log/php_errors.log

# Expose port 80
EXPOSE 80

### Dockerfile Overview

1. **Base Image**:
– You are using the official `php:8.3-apache` image, which is suitable for running Laravel applications.

2. **Installing PHP Extensions**:
– You've included installation for `gd`, `pdo`, and `pdo_mysql`. This is crucial for handling images and database connections in Laravel.

3. **Apache Configuration**:
– The command `a2enmod rewrite` enables URL rewriting, which is necessary for Laravel's routing to function correctly.

4. **Composer**:
– You are copying Composer from the latest image, which is a good practice to ensure you have the latest version.

5. **Working Directory**:
– Setting the working directory to `/var/www/html` is standard for web applications.

6. **File Permissions**:
– You are correctly setting permissions for the storage and cache directories, which is vital for Laravel to write logs and cache data.

7. **Custom Apache Configuration**:
– You included a step to copy a custom Apache virtual host configuration. Ensure that `vhost.conf` is correctly set up to handle Laravel requests. Here’s a simple example of what it might look like:

<VirtualHost *:80>
       DocumentRoot /var/www/html/public
       <Directory /var/www/html/public>
           AllowOverride All
           Require all granted
       </Directory>
       ErrorLog ${APACHE_LOG_DIR}/error.log
       CustomLog ${APACHE_LOG_DIR}/access.log combined
   </VirtualHost>

8. **Custom php.ini**:
– Ensure that your `php.ini` has necessary configurations suitable for a Laravel environment, such as increasing memory limits and enabling necessary extensions.

9. **Logging**:
– You are creating a log file for PHP errors and giving it full permissions. This is useful for debugging but consider changing permissions for security in a production environment.

### Suggested Improvements

1. **Layer Caching**:
– If your project files change often, consider structuring your `COPY` commands to take advantage of Docker’s layer caching. For example, copy the `composer.json` and `composer.lock` files first, run `composer install`, and then copy the rest of the application files.

2. **Environment Variables**:
– For sensitive information like database credentials, consider using environment variables instead of hardcoding them in your `docker-compose.yml` file.

3. **Health Checks**:
– You might want to add a health check to ensure that your application is running as expected.

4. **Entry Point**:
– If you need to run any migrations or seeders automatically when the container starts, you can create an entry point script.

5. **Caching**:
– If your application grows, consider setting up caching strategies for performance improvement.

### Final Dockerfile Example

Here’s an example that incorporates some of the suggestions:

# Use the official PHP image with Apache
FROM php:8.3-apache

# Install PHP extensions and enable necessary Apache modules
RUN apt-get update && apt-get install -y 
        libpng-dev 
        libjpeg-dev 
        libfreetype6-dev 
    && docker-php-ext-configure gd --with-freetype --with-jpeg 
    && docker-php-ext-install gd pdo pdo_mysql 
    && a2enmod rewrite

# Install Composer
COPY --from=composer:latest /usr/bin/composer /usr/bin/composer

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

# Copy composer files first for better caching
COPY shareyourthoughts/composer.json shareyourthoughts/composer.lock ./
RUN composer install --no-dev --optimize-autoloader

# Copy existing application directory permissions
COPY --chown=www-data:www-data shareyourthoughts/ /var/www/html

# Set permissions for storage and cache
RUN chown -R www-data:www-data /var/www/html/storage /var/www/html/bootstrap/cache 
    && chmod -R 775 /var/www/html/storage /var/www/html/bootstrap/cache

# Copy custom Apache configuration if needed
COPY ./apache/vhost.conf /etc/apache2/sites-available/000-default.conf

# Copy custom php.ini
COPY ./php-config/php.ini /usr/local/etc/php/

# Set permissions for logs
RUN mkdir -p /var/log && touch /var/log/php_errors.log && chmod 777 /var/log/php_errors.log

# Expose port 80
EXPOSE 80

### Next Steps

– After adjusting the Dockerfile, make sure to rebuild your Docker image:

docker-compose build

– Then, start your containers:

docker-compose up

Feel free to ask if you have any further questions or need additional assistance!