Environment files (.env) in Docker - Step-by-Step Execution

Process Flow - Environment files (.env)

Create .env file

↓

Add KEY=VALUE pairs

↓

Reference .env in Docker Compose or Dockerfile

↓

Docker reads .env file

↓

Inject environment variables into containers

↓

Containers use variables at runtime

This flow shows how a .env file is created, filled with variables, referenced by Docker, and used inside containers.

Execution Sample

Docker

MY_VAR=hello
VERSION=1.0

# docker-compose.yml snippet
services:
  app:
    environment:
      - MY_VAR
      - VERSION

Defines environment variables in a .env file and uses them in a Docker Compose service.

Process Table

Step	Action	File/Command	Result/Output
1	Create .env file	.env	File created with MY_VAR=hello and VERSION=1.0
2	Write variables	.env	MY_VAR and VERSION set in file
3	Reference .env in docker-compose.yml	docker-compose.yml	Environment keys MY_VAR and VERSION listed
4	Run docker-compose up	docker-compose up	Docker reads .env and injects variables
5	Container starts	docker container	Container environment has MY_VAR=hello, VERSION=1.0
6	Use variables inside container	docker exec app env	Output shows MY_VAR=hello and VERSION=1.0
7	Exit	-	Process ends after container runs with env variables

💡 Container started with environment variables injected from .env file

Status Tracker

Variable	Start	After Step 2	After Step 5	Final
MY_VAR	undefined	hello	hello	hello
VERSION	undefined	1.0	1.0	1.0

Key Moments - 2 Insights

Why doesn't Docker automatically know about variables in the .env file without referencing them?

Docker only injects variables listed in the docker-compose.yml environment section or Dockerfile. The .env file defines variables but they must be explicitly referenced to be used, as shown in step 3 and 4.

What happens if a variable is in the .env file but not listed in docker-compose.yml?

That variable is ignored and not passed to the container environment. Only variables listed under environment in docker-compose.yml are injected, as seen in step 4 and 5.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of MY_VAR inside the container at step 6?

A undefined

B hello

C VERSION

D empty string

💡 Hint

Check the 'Use variables inside container' row in execution_table showing MY_VAR=hello

At which step does Docker read the .env file and inject variables into the container?

A Step 4

B Step 2

C Step 1

D Step 6

💡 Hint

Look at the 'Run docker-compose up' step where Docker reads .env and injects variables

If you remove VERSION from the environment list in docker-compose.yml, what happens to VERSION inside the container?

A It remains 1.0

B It becomes empty string

C It becomes undefined

D Container fails to start

💡 Hint

Refer to key_moments explaining variables not listed in docker-compose.yml are ignored

Concept Snapshot

Environment files (.env) store key=value pairs.
Docker reads .env when running docker-compose or Dockerfile.
Variables must be referenced in docker-compose.yml or Dockerfile to be used.
Containers get these variables injected at runtime.
Useful for separating config from code.

Full Transcript

This visual execution shows how environment files (.env) work with Docker. First, you create a .env file and add variables like MY_VAR=hello and VERSION=1.0. Then, you reference these variables in your docker-compose.yml under the environment section. When you run docker-compose up, Docker reads the .env file and injects the variables into the container environment. Inside the container, you can see these variables with commands like 'env'. Variables not listed in docker-compose.yml are ignored. This method helps keep configuration separate and easy to change without modifying code.

Practice

1. What is the main purpose of a .env file in Docker?

easy

A. To list all running Docker containers

B. To write Docker commands for building images

C. To store environment variables outside the Dockerfile for easy configuration

D. To define network settings for Docker

Solution

1. Step 1: Understand the role of .env files

   .env files hold environment variables separately from code or Dockerfiles, making it easy to change settings without editing code.

2. Step 2: Identify the correct purpose in Docker context

   Docker uses .env files to load environment variables into containers, not for commands, container lists, or network settings.

3. Final Answer:

   To store environment variables outside the Dockerfile for easy configuration -> Option C

4. Quick Check:

   .env files = environment variables storage [OK]

Hint: Think: .env means environment variables outside code [OK]

Common Mistakes:

• Confusing .env with Dockerfile commands
• Thinking .env lists containers or networks
• Assuming .env files run commands

2. Which of the following is the correct syntax for a line in a .env file?

easy

A. MY_VAR = value

B. MY_VAR: value

C. MY_VAR=>value

D. MY_VAR=value

Solution

1. Step 1: Recall .env file syntax rules

   Each line must be a key-value pair with no spaces around the equal sign, like KEY=value.

2. Step 2: Check each option

   MY_VAR=value uses no spaces and an equal sign, which is correct. The other options use spaces, colon, or arrow separators, which are incorrect.

3. Final Answer:

   MY_VAR=value -> Option D

4. Quick Check:

   KEY=value with no spaces [OK]

Hint: No spaces around = in .env lines [OK]

Common Mistakes:

• Adding spaces around equal sign
• Using colon or arrow instead of equal sign
• Using quotes unnecessarily

3. Given a .env file with content:

APP_NAME=MyApp
APP_PORT=8080

and a Docker Compose service using env_file: .env, what will be the value of APP_PORT inside the container?

medium

A. 8080

B. Not set

C. APP_PORT

D. MyApp

Solution

1. Step 1: Understand env_file usage in Docker Compose

   Docker Compose loads variables from the .env file and sets them as environment variables inside the container.

2. Step 2: Identify the value of APP_PORT

   The .env file sets APP_PORT=8080, so inside the container, APP_PORT will be "8080" as a string.

3. Final Answer:

   8080 -> Option A

4. Quick Check:

   APP_PORT = 8080 from .env [OK]

Hint: env_file loads variables exactly as key=value [OK]

Common Mistakes:

• Confusing variable names with values
• Assuming variables are not set inside container
• Mixing up APP_NAME and APP_PORT values

4. You have a .env file with the line DB_PASS=secret pass. When you run your Docker container, the environment variable DB_PASS is not set correctly. What is the likely problem?

medium

A. The space in the value causes parsing issues; values should not contain spaces without quotes

B. The key DB_PASS is invalid because it contains uppercase letters

C. The .env file must be named env.txt to work

D. Docker does not support environment variables from .env files

Solution

1. Step 1: Check .env file value format rules

   Values with spaces must be quoted or use no spaces; otherwise, parsing breaks.

2. Step 2: Identify the issue with the given line

   "secret pass" has a space but no quotes, so Docker reads only "secret" or fails to parse correctly.

3. Final Answer:

   The space in the value causes parsing issues; values should not contain spaces without quotes -> Option A

4. Quick Check:

   Spaces in values need quotes or no spaces [OK]

Hint: No spaces in values unless quoted in .env [OK]

Common Mistakes:

• Ignoring spaces in values
• Thinking uppercase keys are invalid
• Renaming .env file incorrectly

5. You want to use a .env file to set environment variables for multiple Docker Compose services, but one service needs a different value for API_URL. How can you handle this situation?

hard

A. Put all variables in one .env file and override the variable in the Dockerfile

B. Use multiple .env files and specify the correct one per service with env_file in each service definition

C. Use only one .env file and change the variable manually before running Docker Compose

D. Docker Compose does not support different env files per service

Solution

1. Step 1: Understand env_file usage per service

   Docker Compose allows specifying env_file separately for each service to load different environment variables.

2. Step 2: Apply multiple .env files for different services

   Create separate .env files with different API_URL values and assign them to each service using env_file.

3. Final Answer:

   Use multiple .env files and specify the correct one per service with env_file in each service definition -> Option B

4. Quick Check:

   Multiple env_files per service = different variables [OK]

Hint: Use separate env_file per service for different variables [OK]

Common Mistakes:

• Trying to override variables only in Dockerfile
• Editing one .env file manually each time
• Believing Docker Compose can't use multiple env files