How to Fix Docker Environment Variables Not Passing Error

In this tutorial, you'll learn about How to Fix Docker Environment Variables Not Passing Error. We cover key concepts, practical examples, and best practices.

Your container runs but environment variables you set are empty or missing — Docker is not passing the variables due to incorrect syntax, missing --env-file, or shell expansion issues.

The Problem

import os
print(os.getenv("DATABASE_URL"))  # None

The variable was set with export DATABASE_URL=postgres://... on the host but the container does not see it.

Step-by-Step Fix

Step 1: Pass variables with -e

# WRONG — variable not expanded by Docker
docker run -e DATABASE_URL alpine echo $DATABASE_URL

# RIGHT — pass explicit value
docker run -e DATABASE_URL=postgres://localhost:5432/mydb alpine env | grep DATABASE_URL

Expected:

DATABASE_URL=postgres://localhost:5432/mydb

Step 2: Pass host variables to container

export SECRET_KEY=abc123
docker run -e SECRET_KEY alpine env | grep SECRET_KEY

-e SECRET_KEY passes the value from the host environment.

Step 3: Use --env-file for multiple variables

Create .env file:

DATABASE_URL=postgres://db:5432/app
REDIS_URL=redis://cache:6379

Then:

docker run --env-file .env alpine env | grep -E "DATABASE|REDIS"

Step 4: Fix variable expansion in docker-compose.yml

# WRONG — literal string
services:
  app:
    environment:
      - DATABASE_URL

# RIGHT — explicit value
services:
  app:
    environment:
      - DATABASE_URL=postgres://db:5432/app

Step 5: Use env_file in docker-compose.yml

services:
  app:
    env_file:
      - .env

Step 6: Check for special characters

If values contain $ or backticks, use single quotes or escape:

docker run -e PASSWORD='pa$$word' alpine env | grep PASSWORD

Prevention Tips

• Always test with env command inside the container
• Use .env files for multiple variables
• Avoid embedding secrets in compose files
• Use <a href="/devops/docker-compose/">docker compose</a> config to see resolved variables
• Quote values with special characters

Common Mistakes with env vars

1. Misunderstanding that String is [Char] with poor performance for large text operations
2. Using foldl instead of foldl' causing stack overflow on large lists
3. Forgetting deriving (Show, Eq) on custom data types needed for debugging

These mistakes appear frequently in real-world DOCKER code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ