Environment variables precedence in Docker Compose

When the same environment variable is set in multiple sources, Docker Compose follows a precedence rule to determine the value for that variable in your container's environment.

This page contains information on the level of precedence each method of setting environmental variables takes.

The order of precedence (highest to lowest) is as follows:

1. Set using docker compose run -e in the CLI.
2. Set with either the environment or env_file attribute but with the value interpolated from your shell or an environment file. (either your default .env file, or with the --env-file argument in the CLI).
3. Set using just the environment attribute in the Compose file.
4. Use of the env_file attribute in the Compose file.
5. Set in a container image in the ENV directive. Having any ARG or ENV setting in a Dockerfile evaluates only if there is no Docker Compose entry for environment, env_file or run --env.

Simple example

In the following example, a different value for the same environment variable in an .env file and with the environment attribute in the Compose file:

$ cat ./webapp.env
NODE_ENV=test

$ cat compose.yml
services:
  webapp:
    image: 'webapp'
    env_file:
     - ./webapp.env
    environment:
     - NODE_ENV=production

The environment variable defined with the environment attribute takes precedence.

$ docker compose run webapp env | grep NODE_ENV
NODE_ENV=production

Advanced example

The following table uses VALUE, an environment variable defining the version for an image, as an example.

How the table works

Each column represents a context from where you can set a value, or substitute in a value for VALUE.

The columns Host OS environment and .env file is listed only for illustration purposes. In reality, they don't result in a variable in the container by itself, but in conjunction with either the environment or env_file attribute.

Each row represents a combination of contexts where VALUE is set, substituted, or both. The Result column indicates the final value for VALUE in each scenario.

Result explanation

Result 1: The local environment takes precedence, but the Compose file is not set to replicate this inside the container, so no such variable is set.

Result 2: The env_file attribute in the Compose file defines an explicit value for VALUE so the container environment is set accordingly.

Result 3: The environment attribute in the Compose file defines an explicit value for VALUE, so the container environment is set accordingly/

Result 4: The image's ENV directive declares the variable VALUE, and since the Compose file is not set to override this value, this variable is defined by image

Result 5: The docker compose run command has the --env flag set which an explicit value, and overrides the value set by the image.

Result 6: The docker compose run command has the --env flag set to replicate the value from the environment. Host OS value takes precedence and is replicated into the container's environment.

Result 7: The docker compose run command has the --env flag set to replicate the value from the environment. Value from .env file is the selected to define the container's environment.

Result 8: The env_file attribute in the Compose file is set to replicate VALUE from the local environment. Host OS value takes precedence and is replicated into the container's environment.

Result 9: The env_file attribute in the Compose file is set to replicate VALUE from the local environment. Value from .env file is the selected to define the container's environment.

Result 10: The environment attribute in the Compose file is set to replicate VALUE from the local environment. Host OS value takes precedence and is replicated into the container's environment.

Result 11: The environment attribute in the Compose file is set to replicate VALUE from the local environment. Value from .env file is the selected to define the container's environment.

Result 12: The --env flag has higher precedence than the environment and env_file attributes and is to set to replicate VALUE from the local environment. Host OS value takes precedence and is replicated into the container's environment.

Results 13 to 15: The --env flag has higher precedence than the environment and env_file attributes and so sets the value.