Clean up inDelete network atomically · Pull Request !19 · src-openEuler/libnetwork

20.10 backport of libnetwork: clean up inDelete network atomically moby#45310
Fixes Panic in libnetwork during daemon start (panic: runtime error: index out of range [0] with length 0) moby#45057
The (*network).ipamRelease function nils out the network's IPAM info fields, putting the network struct into an inconsistent state. The network-restore startup code panics if it tries to restore a network from a struct which has fewer IPAM config entries than IPAM info entries. Therefore (*network).delete contains a critical section: by persisting the network to the store after ipamRelease(), the datastore will contain an inconsistent network until the deletion operation completes and finishes deleting the network from the datastore. If for any reason the deletion operation is interrupted between ipamRelease() and deleteFromStore(), the daemon will crash on startup when it tries to restore the network.

Updating the datastore after releasing the network's IPAM pools may have served a purpose in the past, when a global datastore was used for intra-cluster communication and the IPAM allocator had persistent global state, but nowadays there is no global datastore and the IPAM allocator has no persistent state whatsoever. Remove the vestigial datastore update as it is no longer necessary and only serves to cause problems. If the network deletion is interrupted before the network is deleted from the datastore, the deletion will resume during the next daemon startup, including releasing the IPAM pools.

(cherry picked from commit moby/moby@c957ad0)

上游补丁pr链接：https://github.com/moby/libnetwork/pull/2677/commits/dbbf124db33cbe4640da59fa03d91902162d7b8e

src-openEuler/libnetwork .gitee-modal { width: 500px !important; }

搜索帮助

src-openEuler/libnetwork