Pass environment variables from docker-compose to container at build stage

I am trying to create configuration for several environments with a single Dockerfile, several docker-compose files and several envoronment_variables files. I need it to use a different file with python dependencies for each environment.

Let’s say, we create a web service in two environments: development and production. To achieve this, I create the following file structure:

  • Kubernetes imagePullSecrets not working; getting “image not found”
  • How to get git repo current tag in Dockerfile during automated build in docker hub
  • Cannot produce message to kafka from service running in docker
  • Determine if new docker container available on docker hub
  • How containerd compares to runC
  • Docker-Compose can't connect to Docker Daemon
  • docker-compose-dev.yml
    docker-compose-prod.yml
    envs/
      dev.env
      prod.env
    web/
      Dockerfile
      requirements_dev.txt 
      requirements_prod.txt
    

    The objective is to instantiate the proper name of a requirements_*.txt file in the Dockerfile during the container’s build process. According to the documentation, I tried this na├»ve approach, which doesn’t seem to work:

    1. Define the name as an environment variable:
      • envs/dev.env: REQUIREMENTS=requirements_dev.txt
      • envs/prod.env: REQUIREMENTS=requirements_prod.txt
    2. Use this environment variable in the Dockerfile:

      FROM python:3.5
      ENV PYTHONUNBUFFERED 1
      ENV APP_ROOT /usr/src/app
      ...
      COPY $REQUIREMENTS $APP_ROOT/
      RUN pip install -r $APP_ROOT/$REQUIREMENTS
      
    3. Import the corresponding definition in a docker-compose configuration:

      version: '2'
      
      services:
          web:
              build: ./web
              env_file:
                  - envs/dev.env   # in docker-compose-dev.yml
                  - envs/prod.env   # in docker-compose-prod.yml
              ...
      

    When I run docker-compose up --build docker-compose-dev.yml, the $REQUIREMENTS variable is not defined at the build process.

    In the docker-compose documentation there is a note on this:

    Note: If your service specifies a build option, variables defined in environment files will not be automatically visible during the build. Use the args sub-option of build to define build-time environment variables.

    But to use the ARG option in the Dockerfile, like ARG REQUIREMENTS, one needs a corresponding args option in docker-compose, like this:

    services:
        web:
            build:
                context: ./web
                args:
                    - REQUIREMENTS
    

    Nevertheless, with this configuration my tests also failed, because, according to the documentation, the value of the REQUIREMENTS variable in Dockerfile is taken from

    the environment where Compose is running

    Therefore, it takes value from my shell, but not from envs/dev.env.

    So my question is:

    Is it possible to pass environment variable from env_file in docker-compose to Dockerfile at build time without setting variables locally in my shell?

  • updating docker image given changes to local filesystem
  • Understanding vagrant with a docker provisioner
  • use docker-client api to start container in Java project
  • Docker Apache 403
  • Why >>> eval “$(docker-machine env default)” in a ansible playbook script return “No such file or directory”
  • How to start docker container in memory?
  • One Solution collect form web for “Pass environment variables from docker-compose to container at build stage”

    Your docker-compose.yml should look like this:

    version: '2'
    services:
      web:
        build:
          context: ./web
          args:
            REQUIREMENTS: "envs/dev.env"
    

    Your Dockerfile should define the build-argument using ARG like this:

    FROM python:3.5
    ENV PYTHONUNBUFFERED 1
    ENV APP_ROOT /usr/src/app
    ARG REQUIREMENTS
    ...
    COPY $REQUIREMENTS $APP_ROOT/
    RUN pip install -r $APP_ROOT/$REQUIREMENTS
    

    I validated this and created a minified functional demo at Github:

    https://github.com/jannikweichert/stackoverflow-41747843

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.