一个Docker容器如何调用另一个Docker容器

Question

I have two Docker containers

1. A Web API
2. A Console Application that calls Web API

Now, on my local web api is local host and Console application has no problem calling the API.However, I have no idea when these two things are Dockerized, how can I possibly make the Url of Dockerized API available to Dockerized Console application?

i don't think i need a Docker Compose because I am passing the Url of API as an argument of the API so its just the matter of making sure that the Dockerized API's url is accessible by Dockerized Console

Any ideas?

Answer 1

This is the best way I have found to connect multiple containers in a local machine / single cluster.

Given: data-provider-service, data-consumer-service

• Option 1: Using Network

docker network create data-network
docker run --name=data-provider-service --net=data-network -p 8081:8081 data-provider-image
docker run --name=data-consumer-service --net=data-network -p 8080:8080 data-consumer-image

Make sure to use URIs like: http://data-provider-service:8081/ inside your data-consumer-service .

• Option 2: Using Docker Compose

You can define both the services in a docker-compose.yml file and use depends_on property in data-provider-service . eg

data-consumer-service:
  depends_on:
    - data-provider-service
     

You can see more details here on my Medium post: https://saggu.medium.com/how-to-connect-nultiple-docker-conatiners-17f7ca72e67f

Answer 2

You can use the link option with docker run :

Run the API:

docker run -d --name api api_image

Run the client:

docker run --link api busybox ping api

You should see that api can be resolved by docker.

That said, going with docker-compose is still a better option.

Answer 3

The idea is not to pass the url, but the hostname of the other container you want to call.
See Networking in Compose

By default Compose sets up a single network for your app. Each container for a service joins the default network and is both reachable by other containers on that network, and discoverable by them at a hostname identical to the container name.

This is what replace the deprecated --link option .

And if your containers are not running on a single Docker server node, Docker Swarm Mode would enable that discoverability across multiple nodes.

Answer 4

The problem can be solved easily if using compose feature. With compose, you just create one configuration file ( docker-compose.yml ) like this :

version: '3'
services:
  db:
    image: postgres
  web:
    build: .
    command: python3 manage.py runserver 0.0.0.0:8000
    volumes:
      - .:/code
    ports:
      - "8000:8000"
    depends_on:
      - db

To make it run, just call up like this :

docker-compose up 

This is the best way to run all your stack, so, check this reference : https://docs.docker.com/compose/

Success!