Environment variables are not set in docker container using docker-compose.yml

Question

I have a .env file like below:

# DEV
SALES_DB_HOST=xxx

Then I have a docker-compose.yml file that looks like:

version: "3.1"
services:
  web:
    image: xxx
    build: .
    env_file: .env

However, the values for the environment variables when accessed in nodejs like process.env.SALES_DB_HOST it prints undefined.

Output of docker-compose config is:

services:
  web:
    build:
      context: xxxxxxxx
    environment:
      SALES_DB_HOST: xxx
    image: xxxxx
version: '3.1'

So, it looks like docker-compose.yml is formed correctly. But why is process.env not getting this value correctly?

EDIT:

I build the docker image with: docker build -t my_image .

Why do you have an extra process.env in there? Does this question help? — BMitch
– BMitch, Commented Jun 8, 2018 at 9:35
@BMitch Sorry, it was a typo in the question. I used process.env.SALES_DB_HOST in my code. — kovac
– kovac, Commented Jun 8, 2018 at 9:53

Maxim Antonov · Accepted Answer · 2018-06-08 10:24:02Z

2

Can you change command on you container configuration in yml file. You should try to test your environment to understand - where is a problem. In docker or in your code.

Try something like this:

maxantonov : ~/passbolt  .$ cat dc.yml
version: '3.4'
services:
  db:
    image: alpine:latest
    container_name: db
    hostname: db
    env_file:
      - env/mysql.env
    command: ["printenv"]

maxantonov : ~/passbolt  .$ docker-compose -f dc.yml up
Starting db ... done
Attaching to db
db    | PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
db    | HOSTNAME=db
db    | MYSQL_ROOT_PASSWORD=test
db    | MYSQL_DATABASE=passbolt
db    | MYSQL_USER=passbolt
db    | MYSQL_PASSWORD=P4ssb0lt
db    | HOME=/root
db exited with code 0

answered Jun 8, 2018 at 10:24

Maxim Antonov

3051 gold badge3 silver badges9 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Maxim Antonov · Accepted Answer · 2018-06-08 09:45:05Z

0

It's not a docker problem. Look to your code:

process.env.process.env.SALES_DB_HOST

It's typo. process.env.process.env

You shold use

process.env.SALES_DB_HOST

answered Jun 8, 2018 at 9:45

Maxim Antonov

3051 gold badge3 silver badges9 bronze badges

1 Comment

kovac Over a year ago

Sorry, the typo was in my question not in the code. I was using process.env.SALES_DB_HOST all along.

Collectives™ on Stack Overflow

Environment variables are not set in docker container using docker-compose.yml

2 Answers 2

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related