Environment files (.env) in Docker - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an environment file (.env) in Docker?

An environment file (.env) is a simple text file that stores key-value pairs used to set environment variables for Docker containers. It helps keep configuration separate from code.

beginner

How do you use a .env file with a Docker Compose file?

You place the .env file in the same directory as the docker-compose.yml file. Docker Compose automatically loads variables from the .env file and replaces them in the compose file where referenced.

beginner

What is the syntax for defining variables inside a .env file?

Each line contains a key and value separated by an equals sign, like VAR_NAME=value. No spaces around the equals sign are allowed.

beginner

How can you reference environment variables from a .env file inside a docker-compose.yml?

Use the syntax ${VAR_NAME} inside the docker-compose.yml file to substitute the value from the .env file.

beginner

Why is it useful to use .env files in Docker projects?

They help keep sensitive data like passwords out of code, make configuration easy to change without editing files, and support different setups for development, testing, and production.

Where should you place the .env file for Docker Compose to automatically load it?

A In the user's home directory

B Inside the Docker image

C In the root of the operating system

D In the same directory as docker-compose.yml

Docker Compose looks for the .env file in the same folder as the docker-compose.yml file.

What is the correct format for a variable in a .env file?

A VAR_NAME=value

B VAR_NAME: value

C VAR_NAME = value

D VAR_NAME => value

The .env file uses key=value format without spaces around the equals sign.

How do you use a variable from a .env file inside docker-compose.yml?

A {{VAR_NAME}}

B $VAR_NAME

C ${VAR_NAME}

D %VAR_NAME%

Docker Compose uses ${VAR_NAME} syntax to substitute environment variables.

Which of these is NOT a benefit of using .env files?

A Making configuration easy to change

B Automatically building Docker images

C Keeping sensitive data out of code

D Supporting different environments like dev and prod

.env files do not build images; they only provide environment variables.

If a variable is missing in the .env file, what happens when Docker Compose tries to use it?

A It leaves the variable empty or uses a default if provided

B Docker Compose crashes immediately

C It replaces the variable with 'null'

D It prompts the user to enter a value

Docker Compose substitutes missing variables with empty strings or defaults if set.

Explain how to create and use a .env file with Docker Compose.

Think about where the file goes and how variables are written and used.

Describe the benefits of using environment files (.env) in Docker projects.

Consider security and flexibility advantages.