how to make a non-hardcoded URL path in docker image to call backend service?

I’m new in docker. Let me describe my scenario:
I made 2 docker images for a web application. one image is front-end web layer for presentation and the other is back-end layer supplying REST service.

So I need to run 2 containers for this 2 images. the front-end calls services in back-end. Now I need to write the back-end’s URL in front-end’s code and build the image…I don’t think this is the right way for micro service…

  • Docker: multiple PHP7-FPM containers on different ports
  • Docker host ip on ubuntu
  • Docker and Rails environments
  • How to check if application has started inside container
  • Can I add new shared directories to Docker from the command line?
  • Issue connecting to rabbitmq from container
  • because if my laptop’s IP changes or others want to use my image,they cannot get the service…So how can I make the URL variable and make my front-end image can be used for others without rebuild?

    Thx!

  • Configuring kubectl against remote clusters
  • Docker base image running slowly Mac OS X
  • Multi-Branch Pipeline project with Jenkinsfile and Docker best practise
  • How to start another bash in Dockerfile
  • Must I create a tunnel to access a docker container on another host?
  • Dump remote MySQL database from a docker container
  • 2 Solutions collect form web for “how to make a non-hardcoded URL path in docker image to call backend service?”

    You can do this by passing an environment variable to the docker container when you run it.

    something like this:

    docker run --name frontend -e MY_APP_BACKEND_IP="192.168.7.2" -e MY_APP_BACKEND_PORT="3000" ...
    

    And on the back-end, let’s say you are using NodeJS, you can do:

    var backend_ip   = process.env.MY_APP_BACKEND_IP;
    

    Note: Not a NodeJS pro, but some googling showed me how to do it

    As of Docker 1.10 you can use networking. What this does is binds the ip address of the docker container to a hostname that can be used in the container.

    If you use docker-compose, a network is automatically created and the two services can talk to one another. Here is an example of one:

    version: "2"
    
    services:
      frontend:
        image: nginx
        networks:
          - my-network
        environment:
          BACKEND_URL: "http://backend"
      backend:
        image: mariadb
        networks:
          - my-network
        environment:
          FRONTEND_URL: "http://frontend"
    
    networks:
      my-network:
        driver: bridge
    

    You can read more about this in the Getting started with multi-host networking available here or you can follow a guide like this Composing Multi-container Networks with Docker Compose

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