Docker not able to remove host IP mapping of the removed containers

[vishr]

Description

Docker engine (swarm mode) is not able to remove host IP mapping of the stopped containers when run using --network-alias option.

Steps to reproduce the issue:

1. Create docker network docker network create --driver overlay --attachable my-network
2. Run three container docker run --network=my-network -it --network-alias app alpine
3. In the last container run apk update && apk add bind-tools && dig app and note the output
4. Now stop first two containers and run Step 1 again, and note the output

Describe the results you received:

;; ANSWER SECTION:
app.			600	IN	A	10.0.1.8
app.			600	IN	A	10.0.1.6
app.			600	IN	A	10.0.1.7

Describe the results you expected:

;; ANSWER SECTION:
app.			600	IN	A	10.0.1.8

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

Happens always. However, if you restart the docker engine in all nodes, the entries are cleared out.

Output of docker version:

root@n1:~# docker version
Client:
 Version:      18.03.1-ce
 API version:  1.37
 Go version:   go1.9.5
 Git commit:   9ee9f40
 Built:        Thu Apr 26 07:17:20 2018
 OS/Arch:      linux/amd64
 Experimental: false
 Orchestrator: swarm

Server:
 Engine:
  Version:      18.03.1-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.5
  Git commit:   9ee9f40
  Built:        Thu Apr 26 07:15:30 2018
  OS/Arch:      linux/amd64
  Experimental: false

Output of docker info:

Containers: 32
 Running: 13
 Paused: 0
 Stopped: 19
Images: 42
Server Version: 18.03.1-ce
Storage Driver: overlay2
 Backing Filesystem: xfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: active
 NodeID: 87iw2hnrqi4jinf5aoc9qaz23
 Is Manager: true
 ClusterID: ctz6hw0fqjzd2d4w4eelh6n4p
 Managers: 1
 Nodes: 3
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
  Force Rotate: 0
 Autolock Managers: false
 Root Rotation In Progress: false
 Node Address: 10.89.0.132
 Manager Addresses:
  10.89.0.132:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 773c489c9c1b21a6d78b5c538cd395416ec50f88
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-93-generic
Operating System: Ubuntu 16.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 94.3GiB
Name: n1
ID: D4CB:4FPJ:AHL4:6Z7G:V6B4:2RBW:VVJV:YRBA:I7PN:RKU2:P6PY:6N2R
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

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

• Physical

[saravana1992]

Hi

In this case can you clear the cache by prune commands and see whether the issue still persists.