fix: ctr run --cni get failed#6670
Conversation
|
Hi @snbc. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Build succeeded.
|
f2f30c8 to
47d7c68
Compare
|
Build succeeded.
|
47d7c68 to
8c7aba2
Compare
when user executes ctr run --cni to start a container,it will call cni plugin to create network .But when user kills it,the network won’t be removed. if we run a container with same namespace and name again will trigger a bug. we should remove the network when user kills task if it enables cni plugin. Fix:containerd#6604 Signed-off-by: SongJiang Han <[email protected]>
|
Build succeeded.
|
8c7aba2 to
2a0b2ee
Compare
|
Build succeeded.
|
when user executes
ctr run --cnito start a container,it will call cni plugin to create network .But when user kills it,the network won’t be removed. if we run a container with same namespace and name again will trigger a bug. we should remove the network when user kills task if it enables cni plugin.Fix:#6604
Signed-off-by: SongJiang Han [email protected]