COPY instruction for adding files in Docker - Step-by-Step Execution

Process Flow - COPY instruction for adding files

Start Dockerfile

↓

Read COPY instruction

↓

Locate source files on host

↓

Copy files into image at destination

↓

Continue building image

↓

Image ready with copied files

The Dockerfile COPY instruction reads source files from your computer and copies them into the image at the specified destination path.

Execution Sample

Docker

COPY ./app /usr/src/app
RUN ls /usr/src/app

Copies the local 'app' folder into the image at '/usr/src/app' and lists its contents.

Process Table

Step	Instruction	Action	Source Path	Destination Path	Result
1	COPY ./app /usr/src/app	Locate and copy files	./app	/usr/src/app	Files copied into image
2	RUN ls /usr/src/app	List files	-	/usr/src/app	Shows copied files
3	-	Build complete	-	-	Image contains /usr/src/app with copied files

💡 COPY completes when all source files are copied to destination inside the image

Status Tracker

Variable	Start	After COPY	After RUN	Final
/usr/src/app contents	empty	files from ./app copied	listed files	files present in image

Key Moments - 3 Insights

Why does COPY fail if the source path is wrong?

COPY looks for files on the host at the exact source path. If the path is wrong, no files are found to copy, so the build fails (see execution_table step 1).

Does COPY preserve file permissions?

Yes, COPY preserves file permissions and metadata when copying files into the image, so files behave as expected inside the container.

Can COPY copy files from URLs or remote locations?

No, COPY only copies files from the local build context (your computer). To get files from URLs, use RUN with curl or wget.

Visual Quiz - 3 Questions

Look at the execution table, what is the source path used in the COPY instruction?

A /app

B ./app

C /usr/src/app

D ./usr/src/app

💡 Hint

Check the 'Source Path' column in execution_table row 1

At which step does the image contain the copied files?

A After build finishes

B Step 2

C Step 1

D Step 3

💡 Hint

Look at the 'Result' column in execution_table rows 1 to 3

If the source path is incorrect, what happens to the build?

A Build continues without copying files

B Files are copied from a default location

C Build fails at COPY step

D COPY instruction is skipped

💡 Hint

Refer to key_moments about COPY failure and execution_table step 1

Concept Snapshot

COPY instruction syntax:
COPY <source_path> <destination_path>
Copies files/folders from local build context into image.
Source path must be relative to build context.
Preserves file permissions.
Fails if source path not found.

Full Transcript

The COPY instruction in Dockerfile copies files from your computer into the image. It reads the source path on your host machine and copies those files into the destination path inside the image. If the source path is wrong, the build fails. After copying, the files are available inside the image at the destination path. This is useful to add your app code or configuration files into the container image.

Practice

1. What does the COPY instruction do in a Dockerfile?

easy

A. It copies files or folders from your computer into the Docker image.

B. It copies files from the Docker image to your computer.

C. It copies environment variables into the container.

D. It copies running containers to new images.

Solution

1. Step 1: Understand the purpose of COPY

   The COPY instruction is used to transfer files or folders from the build context (your computer) into the Docker image during build time.

2. Step 2: Differentiate from other options

   Options A, B, and D describe actions not performed by COPY. COPY does not move files out of the image or handle environment variables or containers directly.

3. Final Answer:

   It copies files or folders from your computer into the Docker image. -> Option A

4. Quick Check:

   COPY moves files into image = C [OK]

Hint: COPY moves files from host to image during build [OK]

Common Mistakes:

• Thinking COPY moves files from image to host
• Confusing COPY with environment variable setting
• Assuming COPY copies running containers

2. Which of the following is the correct syntax to copy a file named app.py from your local folder to /usr/src/app/ inside the Docker image?

easy

A. COPY app.py > /usr/src/app/

B. COPY /usr/src/app/ app.py

C. COPY app.py /usr/src/app/

D. COPY app.py : /usr/src/app/

Solution

1. Step 1: Understand COPY syntax

   The correct syntax is COPY <source> <destination>. The source is the file on your computer, and the destination is the path inside the image.

2. Step 2: Check each option

   COPY app.py /usr/src/app/ correctly uses COPY app.py /usr/src/app/. Options B, C, and D use incorrect order or invalid symbols.

3. Final Answer:

   COPY app.py /usr/src/app/ -> Option C

4. Quick Check:

   COPY source destination = A [OK]

Hint: COPY syntax is COPY source destination [OK]

Common Mistakes:

• Reversing source and destination
• Using symbols like > or : instead of space
• Adding slashes incorrectly

3. Given this Dockerfile snippet:

FROM python:3.12
COPY src/ /app/
RUN ls /app/

What will be the output of RUN ls /app/ if the local folder src contains files main.py and utils.py?

medium

A. src

B. main.py

C. No such file or directory

D. main.py utils.py

Solution

1. Step 1: Understand COPY with folder source

   Using COPY src/ /app/ copies all contents inside src into /app/ inside the image.

2. Step 2: Predict RUN ls output

   Since src contains main.py and utils.py, listing /app/ will show these two files.

3. Final Answer:

   main.py utils.py -> Option D

4. Quick Check:

   COPY folder copies contents = B [OK]

Hint: COPY folder/ dest copies folder contents, not folder itself [OK]

Common Mistakes:

• Expecting folder name to appear inside destination
• Thinking COPY copies folder as a subfolder
• Assuming error if folder exists

4. You wrote this Dockerfile line:

COPY --chown=appuser:appgroup config.yaml /etc/config/

But during build, you get an error: invalid flag: --chown. What is the likely cause?

medium

A. Docker version is too old and does not support --chown flag.

B. The source file config.yaml does not exist.

C. The destination path /etc/config/ is invalid.

D. The --chown flag must be placed after the destination path.

Solution

1. Step 1: Understand --chown flag usage

   The --chown flag sets ownership of copied files but requires Docker version 17.09 or newer.

2. Step 2: Analyze error message

   An 'invalid flag' error usually means the Docker version does not recognize the flag, indicating it is too old.

3. Final Answer:

   Docker version is too old and does not support --chown flag. -> Option A

4. Quick Check:

   Old Docker lacks --chown support = D [OK]

Hint: Check Docker version if --chown flag errors appear [OK]

Common Mistakes:

• Assuming source file missing causes invalid flag error
• Thinking --chown position matters
• Blaming destination path for flag errors

5. You want to copy multiple files index.html and style.css from your local folder into /var/www/html/ inside the Docker image using a single COPY instruction. Which is the correct way?

hard

A. COPY ["index.html", "style.css"] /var/www/html/

B. COPY index.html style.css /var/www/html/

C. COPY index.html /var/www/html/ style.css

D. COPY index.html; style.css /var/www/html/

Solution

1. Step 1: Understand multiple source files syntax

   To copy multiple files, list them separated by spaces before the destination path.

2. Step 2: Evaluate options

   COPY index.html style.css /var/www/html/: COPY index.html style.css /var/www/html/ correctly lists files followed by destination. COPY ["index.html", "style.css"] /var/www/html/ mixes JSON array for sources with space-separated destination, which is invalid syntax. Options C and D have incorrect syntax.

3. Final Answer:

   COPY index.html style.css /var/www/html/ -> Option B

4. Quick Check:

   Multiple files listed before destination = A [OK]

Hint: List multiple files separated by spaces before destination [OK]

Common Mistakes:

• Using JSON array syntax incorrectly
• Placing destination between source files
• Using semicolons instead of spaces