Docker deployment in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the base image for a Laravel Docker container.

Laravel

FROM [1]

Drag options to blanks, or click blank then click option'

Amysql:5.7

Bnode:14

Cubuntu:latest

Dphp:8.1-fpm

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a Node.js or MySQL image as the base image.

Using a generic Ubuntu image without PHP installed.

The base image php:8.1-fpm is commonly used for Laravel applications to run PHP with FastCGI Process Manager.

2fill in blank

medium

Complete the Dockerfile command to copy the Laravel application files into the container.

Laravel

COPY [1] /var/www/html

Drag options to blanks, or click blank then click option'

A.

Bsrc/

Capp/

Dpublic/

Attempts:

3 left

💡 Hint

Common Mistakes

Copying only the src/ or app/ folder which misses other important files.

Copying only the public/ folder which is incomplete.

The COPY . /var/www/html command copies all files from the current directory (where the Dockerfile is) into the container's web root.

3fill in blank

hard

Fix the error in the Dockerfile command to install Laravel dependencies using Composer.

Laravel

RUN composer [1] --no-dev --optimize-autoloader

Drag options to blanks, or click blank then click option'

Aupdate

Binstall

Crequire

Ddump-autoload

Attempts:

3 left

💡 Hint

Common Mistakes

Using composer update which updates packages instead of installing locked versions.

Using composer require which adds new packages.

Using dump-autoload which only regenerates autoload files.

The correct command is composer install to install dependencies listed in composer.json.

4fill in blank

hard

Fill both blanks to expose the correct port and set the working directory in the Dockerfile.

Laravel

EXPOSE [1]
WORKDIR [2]

Drag options to blanks, or click blank then click option'

A8000

B/var/www/html

C8080

D/app

Attempts:

3 left

💡 Hint

Common Mistakes

Exposing port 8080 which is not default for Laravel.

Setting working directory to /app which is not where files are copied.

Laravel's built-in server commonly uses port 8000, and the working directory should be the web root /var/www/html.

5fill in blank

hard

Fill all three blanks to define a Docker Compose service for Laravel with build context, ports, and volumes.

Laravel

services:
  app:
    build: [1]
    ports:
      - "[2]:8000"
    volumes:
      - [3]:/var/www/html

Drag options to blanks, or click blank then click option'

A.

B8000

C./src

D./app

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong build context folder that lacks Dockerfile.

Mapping wrong ports causing connection issues.

Mounting incorrect volume path that misses app files.

The build context is the current directory ., port 8000 is mapped, and the current directory is mounted as a volume to sync files.

Practice

1. What is the main purpose of using Docker for deploying a Laravel application?

easy

A. To package the Laravel app with all its dependencies for consistent environments

B. To write Laravel code faster using special Docker commands

C. To replace Laravel's routing system with Docker's networking

D. To automatically generate Laravel migrations

Solution

1. Step 1: Understand Docker's role in deployment

   Docker packages the app and its environment so it runs the same everywhere.

2. Step 2: Relate this to Laravel deployment

   Laravel apps need PHP, web server, database, and dependencies; Docker bundles these.

3. Final Answer:

   To package the Laravel app with all its dependencies for consistent environments -> Option A

4. Quick Check:

   Docker ensures consistent app environment = C [OK]

Hint: Docker bundles app and tools for same setup everywhere [OK]

Common Mistakes:

• Thinking Docker speeds up coding
• Confusing Docker with Laravel features
• Believing Docker replaces Laravel's internal functions

2. Which file is typically used to define the environment and instructions to build a Docker image for a Laravel app?

easy

A. .env

B. docker-compose.yml

C. Dockerfile

D. composer.json

Solution

1. Step 1: Identify Dockerfile's purpose

   Dockerfile contains commands to build the Docker image step-by-step.

2. Step 2: Differentiate from other files

   docker-compose.yml runs containers; .env holds app configs; composer.json manages PHP packages.

3. Final Answer:

   Dockerfile -> Option C

4. Quick Check:

   Dockerfile builds image = A [OK]

Hint: Dockerfile builds image; compose runs containers [OK]

Common Mistakes:

• Confusing docker-compose.yml with Dockerfile
• Thinking .env defines Docker build steps
• Mixing composer.json with Docker configs

3. Given this docker-compose.yml snippet for Laravel:

services:
  app:
    build: .
    ports:
      - "8000:80"
    volumes:
      - .:/var/www/html
  db:
    image: mysql:8
    environment:
      MYSQL_ROOT_PASSWORD: secret

What happens when you run docker-compose up?

medium

A. It builds the app image, runs app on port 8000, and starts MySQL with root password

B. It only runs MySQL container without the app

C. It builds app image but fails to start MySQL due to missing password

D. It runs app on port 80 without MySQL

Solution

1. Step 1: Analyze docker-compose services

   App service builds from current folder, maps port 8000 to container's 80, mounts code volume. DB uses MySQL image with root password set.

2. Step 2: Understand docker-compose up behavior

   It builds and starts all defined services, so both app and db run with given configs.

3. Final Answer:

   It builds the app image, runs app on port 8000, and starts MySQL with root password -> Option A

4. Quick Check:

   Compose runs all services with configs = B [OK]

Hint: docker-compose up runs all services with given configs [OK]

Common Mistakes:

• Assuming only one service runs
• Missing environment variable for MySQL password
• Confusing port mapping direction

4. You wrote this Dockerfile for Laravel but get an error when building:

FROM php:8.1-fpm
RUN apt-get update && apt-get install -y git zip unzip
COPY . /var/www/html
RUN composer install

What is the likely cause of the build failure?

medium

A. apt-get update should be run after composer install

B. COPY command syntax is incorrect

C. PHP version 8.1-fpm is not supported by Laravel

D. Missing installation of Composer before running composer install

Solution

1. Step 1: Check Dockerfile commands order

   Composer is a separate tool and must be installed before running composer install.

2. Step 2: Identify missing Composer installation

   Dockerfile does not install Composer, so the command fails.

3. Final Answer:

   Missing installation of Composer before running composer install -> Option D

4. Quick Check:

   Composer must be installed before use = D [OK]

Hint: Install Composer before running composer commands [OK]

Common Mistakes:

• Assuming PHP image includes Composer by default
• Thinking COPY syntax causes build error
• Believing PHP 8.1-fpm is incompatible with Laravel

5. You want to deploy a Laravel app with Docker using docker-compose. You need PHP, MySQL, and Redis services. Which docker-compose.yml snippet correctly sets up these services with proper ports and environment variables?

hard

A. services:
app:
image: laravel/php
ports:
- "80:80"
db:
image: mysql
environment:
MYSQL_PASSWORD: secret
cache:
image: redis
ports:
- "6379:6379"

B. services:
app:
build: .
ports:
- "8080:80"
volumes:
- .:/var/www/html
db:
image: mysql:8
environment:
MYSQL_ROOT_PASSWORD: secret
cache:
image: redis:latest
ports:
- "6379:6379"

C. services:
app:
build: .
ports:
- "80:8080"
db:
image: mysql:5.7
environment:
MYSQL_ROOT_PASSWORD: root
cache:
image: redis
ports:
- "6379:6379"

D. services:
app:
build: .
ports:
- "8000:8000"
db:
image: mysql:8
environment:
MYSQL_ROOT_PASSWORD: secret
cache:
image: redis:latest

Solution

1. Step 1: Check app service configuration

   services: app: build: . ports: - "8080:80" volumes: - .:/var/www/html db: image: mysql:8 environment: MYSQL_ROOT_PASSWORD: secret cache: image: redis:latest ports: - "6379:6379" builds app from current folder, maps port 8080 to container port 80, and mounts code volume correctly.

2. Step 2: Verify db and cache services

   MySQL uses image mysql:8 with root password set; Redis uses latest image and exposes default port 6379.

3. Step 3: Compare other options for correctness

   services: app: image: laravel/php ports: - "80:80" db: image: mysql environment: MYSQL_PASSWORD: secret cache: image: redis ports: - "6379:6379". This option misses the volume mount for app code and uses wrong environment variable for MySQL (MYSQL_PASSWORD instead of MYSQL_ROOT_PASSWORD); the option with app ports "80:8080" has wrong port mapping; the option without ports for Redis misses exposing the Redis port.

4. Final Answer:

   services: app: build: . ports: - "8080:80" volumes: - .:/var/www/html db: image: mysql:8 environment: MYSQL_ROOT_PASSWORD: secret cache: image: redis:latest ports: - "6379:6379" -> Option B

5. Quick Check:

   Correct service setup with ports and env = A [OK]

Hint: Check ports and env vars carefully for all services [OK]

Common Mistakes:

• Swapping port mappings (host:container)
• Using wrong environment variable names
• Omitting volume mounts for app code
• Not exposing Redis port