6.3.1 Container Environment
A focused guide to Container Environment, connecting core concepts with practical Docker and container operations.
The container environment is the complete set of environment variables visible to a container's main process at runtime, combining values set in the image through ENV, values supplied at run time through -e or --env-file, and any other variables Docker itself injects automatically.
How the Final Environment Is Assembled
A container's actual environment is built up from multiple sources, with runtime-supplied values generally taking precedence over image defaults for any variable set in both places.
ENV LOG_LEVEL=info
ENV NODE_ENV=production
docker run -e LOG_LEVEL=debug myapp:1.0
The resulting container sees LOG_LEVEL=debug (the runtime override) and NODE_ENV=production (unchanged from the image default), combining both sources into the final, effective environment.
Inspecting a Running Container's Actual Environment
The complete, final environment a running container is actually operating with can be inspected directly, confirming exactly what values are in effect.
docker exec myapp env
Supplying Many Variables Through an Environment File
For configurations involving numerous variables, an environment file avoids needing to specify each one individually as a separate -e flag.
LOG_LEVEL=debug
DATABASE_URL=postgres://localhost/mydb
CACHE_TTL=3600
docker run --env-file local.env myapp:1.0
Why Understanding the Container Environment Matters
A clear understanding of exactly how a container's final environment is assembled — image defaults combined with runtime overrides — is essential for correctly configuring application behavior and for diagnosing situations where a container doesn't seem to be picking up an expected configuration value.