Docker Compose无法读取根目录.env变量用于端口映射求助

安全阿岳

2026-6-15

Problem Cause

Docker Compose handles environment variables in two distinct contexts, which is why your setup isn't working as expected:

Compose file interpolation: Variables used directly in the Compose file (like port mappings) are loaded from three sources only:
- The .env file in the working directory where you run docker compose up
- Variables already present in your shell environment
- Files specified via the --env-file command-line flag
Container runtime variables: The env_file option in the Compose file only passes variables into the running container—it does not make those variables available for Compose to use when parsing the file itself (such as for port mapping configurations).

This explains your observations:

When .env is in the same directory as the Compose file, Compose automatically loads it for interpolation, so the port mapping works.
Using env_file to point to the root .env lets the container see the variable, but Compose can't access it for port mapping, leading to random port assignment.
${DB_PORT:?error} throws an error because Compose can't find the variable in its own loaded environment (it doesn't look at the env_file specified in the Compose file).

Solutions

You can resolve this with one of these practical approaches:

Run Compose from the root directory: Use the -f flag to specify the path to your subdirectory's Compose file. Example:
```
docker compose -f ./subdir/docker-compose.yml up
```
Compose will automatically load the root .env file for interpolation.
Specify the env file via command line: When running from the subdirectory, use --env-file to point to the root .env:
```
docker compose --env-file ../.env up
```
Export the variable in your shell: Set the variable before running Compose so it's available for interpolation:
```
export DB_PORT=5433 && docker compose up
```