http – Docker如何将一个容器发送请求(curl – get,post)到另一个容器

前端之家收集整理的这篇文章主要介绍了http – Docker如何将一个容器发送请求(curl – get,post)到另一个容器前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。

GET(和POST PUT ….)请求在一个容器中使用curl到另一个容器.

$docker ps

CONTAINER ID    IMAGE      COMMAND       PORTS                                           NAMES
b184219cd8f6    otp_totp  "./run.sh"    0.0.0.0:3000->3000/tcp                           totp_api
c381c276593f    service   "/bin/sh -c"  0.0.0.0:8000->8000/tcp,0.0.0.0:9000->9000/tcp   service
d0add6b1c72e    MysqL     "/tmp/run.sh" 0.0.0.0:3306->3306/tcp                           MysqL

当我发送请求curl -X GET http://localhost.3000到本地的totp_api容器时

totp_api返回{‘status’:200}

但我想在服务容器中发送请求

比如// curl -X GET http:// localhost:3000到服务中的totp_api容器(docker exec -it / bin / bash),totp_api会将{‘status’:200}返回给服务器容器

project_folder
             ㄴ- docker-compose.yml # service,MysqL container
api_folder
         ㄴ- docker-compose.yml # totp_api container

请一些人告诉我一些建议

API /文件夹/搬运工-compose.yml

version: '3'
services:
    totp:
        build: .
        container_name: totp_api
        volumes:
            - $PWD:/home
        ports:
            - "3000:3000"
        tty: true
        restart: always
        networks:
            - bridge

networks:
    bridge:
        driver: bridge

$docker-compose up -d
$docker network ls

NETWORK ID          NAME                DRIVER              SCOPE
4a05be5e600f        bridge              bridge              local
503d0586c7ec        host                host                local
########            ####
727bfc6cc21f        otp_bridge          bridge              local
########            ####
3c19d98d9ca5        otp_default         bridge              local

$docker network inspect otp_bridge

[
    {
        "Name": "otp_bridge","Id": "727bfc6cc21fd74f19eb7fe164582637cbad4c2d7e36620c1c0a1c51c0490d31","Created": "2017-12-13T06:12:40.5070258Z","Scope": "local","Driver": "bridge","EnableIPv6": false,"IPAM": {
                "Driver": "default","Options": null,"Config": [
                    {
                        "Subnet": "172.19.0.0/16","Gateway": "172.19.0.1"
                    }
                ]
            },"Internal": false,"Attachable": true,"Ingress": false,"ConfigFrom": {
                "Network": ""
            },"ConfigOnly": false,"Containers": {
        "02fa407062cdd5f6f368f2d17c5e68d2f9155d1d9b30c9edcbb2386a9ded648a": {
                "Name": "totp_api","EndpointID": "860c47da1e70d304399b42917b927a8cc6717b86c6d1ee6f065229e33f496c2f","MacAddress": "02:42:ac:13:00:02","IPv4Address": "172.19.0.2/16","IPv6Address": ""
            }
        },"Options": {},"Labels": {
            "com.docker.compose.network": "bridge","com.docker.compose.project": "otp"
        }
    }
]
使用docker networkingnetwork commands,您可以确保这些容器属于同一网络.

该唯一网络的副作用是容器A将知道容器B名称:从totp_api,您可以使用其名称ping或卷曲服务容器:

ping service

您可以:

>在docker compose文件中静态执行(并重新启动新容器),– 在运行时测试它,将现有的运行容器添加到新网络

原文链接:https://www.f2er.com/docker/436686.html

猜你在找的Docker相关文章