Hi everyone! I’m facing an issue with docker-compose and env_file: directive that is driving me crazy. I’ve this simple docker-compose.yml file: version: "3.3" services: prometheus: image: "prom/prometheus:latest" container_name: "prometheus" env_file: - prometheus/conf.d/prom…

Good morning, I guess that your prometheus/conf.d/prometheus.env-file sets the ENV-variables LISTEN_ADDRESS and LISTEN_PORT on your Docker-host. These variables are then used within your docker-compose.yml within the command:-line. So without the env-file the two ENV-variables on your host are emp…

[image] matthiasradde: So without the env -file the two ENV-variables on your host are empty Yes, but if I understand the question correctly, the Compose file defines the following: env_file: - prometheus/conf.d/prometheus.env Also, docker-compose config shows it knows where to fi…

@avbentem You are right - Sorry I didn’t spot the env_file: in the docker-compose.yml When was the parameter --env-file and the env_file: introduced to docker-compose? With Docker version 20.10.7 docker-compose version 1.29.2, build 5becea4c both options are available whereas with Docker version…

[image] matthiasradde: But .env and ENV-variables on the Docker-host are working there, too. I prefer using .env, especially when Dockerfiles and all are in Git, and one can easily create a local configuration in a local .env (and docker-compose.override.yml), without fearing accidentally com…

Thank you so much everyone participating, your thoughts and ideas help a lot. However I’ve tested escaping the vars as suggested and it doesn’t work neither. I’m really confused by the way docker-compose take the file, create the env vars but yet you can’t use them. Am I supposed to use them with…

Odd, escapping should have worked. You can find the documatation about escaping the $ character at the end of the variable-substitution chapter in the compose file reference I used it in the past, though don’t realy remember if it was in combination with a .env file or an env_file: declaration or …

I filled a bug with prometheus team as I tested the behavior with a hand made container using Ubuntu and dumb-init to just launch a command as: command: [ 'bash', '-c', 'echo "$${LISTEN_ADDRESS}:$${PORT}"' ] using only env_file directive and it works! So I guess it may be a hiccup with the way Al…

[image] gtherond: using only env_file directive and it works! Does docker-compose config also show the substituted values for that minimal example? (Just curious if config always works as expected for debugging.)

So, docker-compose config output as is: services: debug: build: context: /home/flint/services/debug command: - bash - -c - echo "$${LISTEN_ADDRESS}:$${LISTEN_PORT}" container_name: debug environment: LISTEN_ADDRESS: 192.168.1.74 LISTEN_PORT: '9090' …

Docker-compose env_file behavior is confusing

General

meyay (Metin Y.) August 7, 2021, 8:24am 4

Well spotted!

the $ signs in the command must be escapped with another $ sign to delay the point where the variable expansion takes place into the containar:
This should work: "--web.listen-address=$${LISTEN_ADDRESS}:$${LISTEN_PORT}"

.env file not read

Topic		Replies	Views
Additional property env_files is not allowed Compose docker , docker-compose	1	10586	March 29, 2023
Docker compose with environment file gives unexpected results General	2	248	September 16, 2024
Final environment variables applied file is needed Docker Desktop	6	194	May 31, 2024
Inconsistent handling of environment variables General docker-compose	1	273	October 24, 2024
.env file not read General	2	2154	October 19, 2021

Docker-compose env_file behavior is confusing

Related topics