dongyixiu3110 2017-05-11 09:40
浏览 577

无法连接到在本地Docker容器中运行的Go GRPC服务器

I have a go grpc service. I'm developing on a mac, sierra. When running a grpc client against the service locally, all is well, but when running same client against same service in the docker container I get this error:

transport: http2Client.notifyError got notified that the client transport was broken EOF.
FATA[0000] rpc error: code = Internal desc = transport is closing

this is my docker file:

FROM golang:1.7.5

RUN mkdir -p /go/src/
WORKDIR /go/src/

COPY . /go/src/
# ONBUILD RUN go-wrapper download
RUN go install

ENTRYPOINT /go/bin/bar

EXPOSE 51672

my command to build the image:

docker build -t bar .

my command to launch the docker container:

docker run -p 51672:51672 --name bar-container bar

Other info:

  • client program runs fine from within the docker container
  • connecting to a regular rest endpoint works fine (http2, grpc related?)
  • running the lsof command in OS X yields these results

    $lsof -i | grep 51672
    com.docke   984 oldDave   21u  IPv4 0x72779547e3a32c89      0t0  TCP *:51672 (LISTEN)
    com.docke   984 oldDave   22u  IPv6 0x72779547cc0fd161      0t0  TCP localhost:51672 (LISTEN)
  • here's a snippet of my server code:

    server := &Server{}
    endpoint := "localhost:51672"
    lis, err := net.Listen("tcp", endpoint)
    if err != nil {
        log.Fatalf("failed to listen: %v", err)
    s := grpc.NewServer(grpc.Creds(creds))
    pb.RegisterExpServiceServer(s, server)
    // Register reflection service on gRPC server.
    log.Info("Starting Exp server: ", endpoint)
    if err := s.Serve(lis); err != nil {
        log.Fatalf("failed to serve: %v", err)
  • 写回答

1条回答 默认 最新

  • doushi4956 2017-05-12 11:28

    When you specify a hostname or IP address​ to listen on (in this case localhost which resolves to, then your server will only listen on that IP address.

    Listening on localhost isn't a problem when you are outside of a Docker container. If your server only listens on, then your client can easily connect to it since the connection is also made from

    When you run your server inside a Docker container, it'll only listen on as before. The is a local loopback address and it not accessible outside the container.

    When you fire up the docker container with "-p 51672:51672", it'll forward traffic heading to to the container's IP address, which in my case is

    The container gets an IP addresses within the docker0 network interface (which you can see with the "ip addr ls" command)

    So, when your traffic gets forwarded to the container on, there's nothing listening there and the connection attempt fails.

    The fix:

    The problem is with the listen endpoint:

    endpoint := "localhost:51672"

    To fix your problem, change it to

    endpoint := ":51672"

    That'll make your server listen on all it container's IP addresses.

    Additional info:

    When you expose ports in a Docker container, Docker will create iptables rules to do the actual forwarding. See this. You can view these rules with:

    iptables -n -L 
    iptables -t nat -n -L
    本回答被题主选为最佳回答 , 对您是否有帮助呢?



  • ¥65 LineageOs-21.0系统编译问题
  • ¥30 关于#c++#的问题,请各位专家解答!
  • ¥15 App的会员连续扣费
  • ¥15 不同数据类型的特征融合应该怎么做
  • ¥15 用proteus软件设计一个基于8086微处理器的简易温度计
  • ¥15 用联想小新14Pro
  • ¥15 multisim中关于74ls192n和DSWPK开关仿真图分析(减法计数器)
  • ¥15 w3wp,exe 中发生未处理的 Microsoft ,NETFramework 异常。
  • ¥20 C51单片机程序及仿真(加减器)
  • ¥15 AQWA | 水动力分析 二阶波浪力