Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple containers getting same IP #37743

Open
sunilthemaster opened this issue Sep 1, 2018 · 2 comments
Open

Multiple containers getting same IP #37743

sunilthemaster opened this issue Sep 1, 2018 · 2 comments

Comments

@sunilthemaster
Copy link

Description
Multiple containers getting same IP

We have an issue in PRODUCTION environment wherein, when we are trying to ping a container from another container, we are getting 2 different container IDs in response. One of the container is alive and other does not even exists.
image

Even we killed sensu_client container but still it's pinging to that particular container.

Steps to reproduce the issue:
Not sure how we can replicate the issue.

Describe the results you received:
image

Describe the results you expected:
There should be only 1 IP per container

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

Output of docker version:

Client:
 Version:       18.03.0-ce
 API version:   1.37
 Go version:    go1.9.4
 Git commit:    0520e24
 Built: Wed Mar 21 23:10:01 2018
 OS/Arch:       linux/amd64
 Experimental:  false
 Orchestrator:  swarm

Server:
 Engine:
  Version:      18.03.0-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.4
  Git commit:   0520e24
  Built:        Wed Mar 21 23:08:31 2018
  OS/Arch:      linux/amd64
  Experimental: false

Output of docker info:

Containers: 12
 Running: 4
 Paused: 0
 Stopped: 8
Images: 28
Server Version: 18.03.0-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: false
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: active
 NodeID: wrqykt7b42zbrpo4mqfz2sp54
 Is Manager: true
 ClusterID: 9lh6kgdspjfughhmgvtevp1we
 Managers: 3
 Nodes: 20
 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.100.6.4
 Manager Addresses:
  10.100.6.4:2377
  10.100.6.5:2377
  10.100.6.6:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfd04396dc68220d1cecbe686a6cc3aa5ce3667c
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.15.0-1013-azure
Operating System: Ubuntu 16.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 6.784GiB
Name: az-prod-mgr-000000
ID: IPZJ:2GQL:OC6Z:UDSS:4OAE:PF46:AAAP:JVYF:4RJG:5JQA:QLWW:XWW2
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.):
It's on Azure Linux VMs

@sunilthemaster
Copy link
Author

Any updates? or any comments?

@sunilthemaster
Copy link
Author

@thaJeztah : Can you please check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant