Skip to content

docker-containerd started occupying port 10010 #37507

@kosciak9

Description

@kosciak9

Description

We are using docker with docker-compose for our services (GitLab, Wiki, etc).
Every service is using port from 10010 to 10050 (we jump by ten for every service) and it is sitting behind Nginx for reverse proxy. It worked nice, but yesterday I have added new service at port 10050 and after reboot I'm unable to start GitLab on 10010, as it keeps erroring on Error starting userland proxy: listen tcp 0.0.0.0:10010: bind: address already in use. Process using port 10010 is docker-containerd. I have moved GitLab to 10060 and it works currently. Why did docker-containerd started ocupying port 10010? Is it configurable?

Steps to reproduce the issue:
I'm unsure. I had five services (10010 and 10011, 10020, 10030, 10040, 10050). Rebooted machine.

Describe the results you received:
Port 10010 is used even though no container is using it.

Describe the results you expected:
Port 10010 is free and ready to bind.

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

Client:
 Version:           18.06.0-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        0ffa825
 Built:             Wed Jul 18 19:11:02 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.0-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       0ffa825
  Built:            Wed Jul 18 19:09:05 2018
  OS/Arch:          linux/amd64
  Experimental:     false

Output of docker info:

Containers: 16
 Running: 10
 Paused: 0
 Stopped: 6
Images: 76
Server Version: 18.06.0-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: d64c661f1d51c48782c9cec8fda7604785f93587
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-130-generic
Operating System: Ubuntu 16.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.42GiB
Name: luna
ID: 6H36:M6K6:T2XY:PCPQ:23KJ:LCLS:TE3K:GLV3:6SLF:OWQ6:3IM4:S4AF
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):

  • physical server
  • Ubuntu 16.04.5 LTS

I will happily provide any details needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/runtimeRuntimekind/enhancementEnhancements are not bugs or new features but can improve usability or performance.version/18.06

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions