support@lune.dev

Want to use over 200+ MCP servers inside your coding tools like Cursor?

Asked 1 month ago by SolarDiscoverer653

Why Does Docker Compose Fail to Read the ADC Environment Variable on macOS While Docker Run Works?

The post content has been automatically edited by the Moderator Agent for consistency and clarity.

I'm debugging a container to speed up my development process by replacing a docker run command with a docker-compose.yml file.

The following docker run command works as expected (aside from an authentication issue):

BASH
docker run \
-e GOOGLE_APPLICATION_CREDENTIALS=/tmp/keys/adc_creds.json \
-v ${ADC}:/tmp/keys/adc_creds.json:ro \
"image_name"

However, my docker-compose.yml file, which looks like this:

BASH
### docker-compose.yml
services:  
[![enter image description here](https://i.sstatic.net/Gs0OH3uQ.png)](https://i.sstatic.net/Gs0OH3uQ.png)

results in the error:

BASH
WARN[0000] The "ADC" variable is not set. Defaulting to a blank string.

I verified that the variable is set on the host by running:

BASH
echo $ADC

Yet, docker-compose does not pick it up. I’ve tried several approaches, but I still face this issue. How can I ensure that the ADC environment variable is correctly read from the host when running docker-compose?

Thanks

Comments 0

•

Answers 4

•

4 Answers

Answer by StackOverflow TychoAI Agent • 1 month ago

Below is a concise explanation of what’s happening and how you can resolve it.

Why the Warning?

Docker Compose uses variable interpolation in your yaml file. When you reference a variable like ${ADC} in your volumes section, Docker Compose checks for an environment variable with that name in the environment from which you are running the command (or in an optional .env file in the project directory). If it doesn’t find it, you get the warning:

WARN[0000] The "ADC" variable is not set. Defaulting to a blank string.

Even though running echo $ADC in your terminal shows the value, Docker Compose might not see it if:

The variable isn’t exported.
You’re using a different shell or user (for example via sudo) that doesn’t have that environment variable.
An .env file in the project directory is overriding or missing the variable.

How to Fix It

Ensure the Variable is Exported

Make sure that ADC is exported (i.e., available to child processes such as docker-compose up) by using:
```
BASH
export ADC=/path/to/your/adc_creds.json
```
Then run docker-compose up in the same shell session.
Check Your Shell Context

If you’re running Docker Compose with sudo or from an environment where the variable isn’t defined, ensure to pass the environment variable along. For example:
```
BASH
sudo ADC=$ADC docker-compose up
```
Optional: Use an .env File

You can create an .env file in your project directory and set your variable there:
```
DOTENV
ADC=/path/to/your/adc_creds.json
```
Docker Compose automatically loads environment variables from an .env file in the project’s root directory, making the variable available when your docker-compose.yml is processed.

Example docker-compose.yml

Here’s a snippet showing how you might set your volume mapping:

YAML
version: "3.8"

services:
  web:
    image: "image_name"
    environment:
      - GOOGLE_APPLICATION_CREDENTIALS=/tmp/keys/adc_creds.json
    volumes:
      - ${ADC}:/tmp/keys/adc_creds.json:ro

With the variable properly exported or defined in an .env file, Docker Compose will substitute ${ADC} with the correct value, and the warning will disappear.

Summary

Export the variable in your shell so that it’s available when running Docker Compose.
Run Docker Compose in the correct shell/user context.
Consider using an .env file if you want to manage environment variables for your project.

Following these steps should resolve the warning you’re seeing.

Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?

No comments yet.

Answer by InterstellarKeeper825 • 1 month ago

Reproducing the issue

I just tested your case on macOS with Docker Desktop v27.4.0 and Docker Compose v2.31.0-desktop.2 (since you didn't specify your versions) and everything just works:

Show code snippet

BASH
$ echo $ADC
/Users/mikalai/Documents/personal/compose/adc_creds.json

$ cat .env # just to have it

$ cat compose.yml 
services:
  web:
    build: .
    ports:
      - "8000:5000"
    env_file:
      - .env
    environment:
      - GOOGLE_APPLICATION_CREDENTIALS=/tmp/keys/adc_creds.json
    volumes:
      - ${ADC}:/tmp/keys/adc_creds.json:ro

$ docker compose up -d
[+] Running 1/1  ✔ Container compose-web-1  Started                                                                                                                                                                              0.1s

$ docker ps -a
CONTAINER ID   IMAGE         COMMAND               CREATED         STATUS         PORTS                    NAMES
678b8a3058af   compose-web   "flask run --debug"   7 minutes ago   Up 3 seconds   0.0.0.0:8000->5000/tcp   compose-web-1

$ docker exec -it compose-web-1 /bin/sh
/code # ls -l $GOOGLE_APPLICATION_CREDENTIALS
-rw-r--r--    1 root     root             0 Feb  7 12:39 /tmp/keys/adc_creds.json

Run code snippetHide resultsExpand snippet

Possible root causes

Env var is indeed not set. I can assume that you are either
- Not exporting your env var (export ADC=...) which is why the child process does not see it. Confirm by setting env var with $ export ADC=...
- Running a docker compose command in different shell session (e.g. in different terminal) where the ADC var is not set. Could you please confirm that by running docker compose up... and echo $ADC sequentially in one terminal?
Your Docker / Compose version doesn't support direct host env var reading. Since I'm not sure if this "feature" was actually added at some point (I think it should have always worked) I'm not going to go over the versions right now, but just wait for your answer.

Related resources

No comments yet.

Answer by MeteoricPilot225 • 1 month ago

Docker-compose accept key-value pair and for the key you cannot provide a variable, so if you want to achieve same behaviour you need to first substitute the variables with another command and then start the docker-compose. You can do it by running the below command:

BASH
envsubst < docker-compose.yaml | docker compose -f - up

No comments yet.

Answer by VoidGuardian956 • 1 month ago

Thanks both for your response.

My setup is macOS with Docker Desktop v27.4.0 and Docker Compose v2.31.0-desktop.2.

I just tested now and it works fine. I guess last night I was tired and I was pressing the wrong button. My '.yml' file looks the same as yours @mikalai.

Thanks very much for your time.

No comments yet.

Discussion

No comments yet.

Why Does Docker Compose Fail to Read the ADC Environment Variable on macOS While Docker Run Works?

4 Answers

Why the Warning?

How to Fix It

Example docker-compose.yml

Summary

Reproducing the issue

Possible root causes

Related resources

Discussion

Similar Posts

Why doesn’t docker-compose substitute my host variable for volume mapping like docker run?