Skip to content

Why does docker-containerd listen on external interface ? #2483

@zerthimon

Description

@zerthimon

I'm not sure this is a correct repo to post this question, but anyway...
I have a server with internal (private network) and external (direct internet connection) interfaces.

After I start docker.service I observe docker-containerd process listening on an external IP, and is directly accessible from the internet.

tcp        0      0 5.00.209.17:10010       0.0.0.0:*               LISTEN      26345/docker-contai

If I run another instance of docker-containerd it says:

ERRO[0000] Failed to start streaming server              error="listen tcp 5.00.209.17:10010: bind: address already in use"
FATA[0000] Failed to run CRI service                     error="stream server error: listen tcp 5.00.209.17:10010: bind: address already in use"

So, how do I configure this to listen on internal IP instead ?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions