-
Notifications
You must be signed in to change notification settings - Fork 85
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
docker may left orphaned veth interface after container deletion #109
Comments
Any updates on this issue? |
unable to reproduce this issue with |
@arkodg
|
Mine instance has bunch of these orphanated interfaces....
|
Expected behavior
Deleting container should delete container's veth interface
Actual behavior
Container is deleted, but it's veth interface exists
Description
Sometimes we reach situation when docker leaves uncleaned veth interfaces. Container stuck in state deleting or it is even deleted, but some of theirs data and interfaces stays in a system.
This situation causes some troubles with creating new containers, i.e reaching limit of 1023 interfaces in same bridge. It's possible to reach situation when there is few hundreds of orphaned interfaces. Mentioned veth[a-f0-9]+ disappears after restarting docker service.
Steps to reproduce the behavior
Instruction
please download script from: https://github.com/n0npax/docker-ce-orphaned-veth-gen-script/blob/master/veth-docker.sh
Script will delete all docker containers and generate issue.
If you have bare ubuntu16.04 you may also run script from: https://github.com/n0npax/docker-ce-orphaned-veth-gen-script/blob/master/veth-docker-prepare.sh
In other case please install docker-ce and start docker service on your own.
sample script output
generated issue looks like:
Output of
docker version
:Output of
docker info
:**Additional environment details **
Able to reproduce on:
The text was updated successfully, but these errors were encountered: