Java System.getenv does not resolve environment variable defined in docker-compose

Question

I have this sample docker-compose.yml:

version: "2"

networks:
  default:
    external:
      name: simple-monitor_zeebe_network

services:
  ods:
    container_name: auto-auction-service
    image: cargeeks/auto-auction-service:SNAPSHOT
    environment:
      - SERVICE_LOG_LEVEL=debug
      - client.broker.contactPoint=172.20.0.6:26500
    ports:
      - "9200:7100"
    networks:
      - default

Somewhere in my microservice, I have code like this which attempts to resolve the client.broker.contactPoint environment variable.

 String contactPoint = System.getenv("client.broker.contactPoint");
            if (StringUtils.isEmpty(contactPoint)) {
                _logger.info("Environment variable " + ENV_CONTACT_POINT + " is not defined.  Using default " + DEFAULT_CONTACT_POINT);
                contactPoint = DEFAULT_CONTACT_POINT;
            }

When I run docker-compose up against the docker-compose.yml file defined above, the contactPoint is always defined to the DEFAULT_CONTACT_POINT.

What am I doing wrong here?

Ramsay Domloge · Accepted Answer · 2020-01-09 19:16:44Z

2

Try without a dot-separated variable name. Some environments either do no allow this or try and interpret them as a hierarchical reference. Use underscores instead, both in the Docker-compose file and the code.

answered Jan 9, 2020 at 19:16

Ramsay Domloge

8054 silver badges11 bronze badges

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

1 Comment

Klaus Nji Over a year ago

Yea, that was the problem. CLIENT_BROKER_CONTACT_POINT works instead.

Collectives™ on Stack Overflow

Java System.getenv does not resolve environment variable defined in docker-compose

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related