557a6b4a5e
This PR fixes a bug where the docker network pause container would not be stopped and removed in the case where a node is restarted, the alloc is moved to another node, the node comes back up. See the issue below for full repro conditions. Basically in the DestroyNetwork PostRun hook we would depend on the NetworkIsolationSpec field not being nil - which is only the case if the Client stays alive all the way from network creation to network teardown. If the node is rebooted we lose that state and previously would not be able to find the pause container to remove. Now, we manually find the pause container by scanning them and looking for the associated allocID. Fixes #17299 |
||
|---|---|---|
| .. | ||
| interfaces | ||
| state | ||
| tasklifecycle | ||
| taskrunner | ||
| alloc_runner.go | ||
| alloc_runner_hooks.go | ||
| alloc_runner_test.go | ||
| alloc_runner_unix_test.go | ||
| allocdir_hook.go | ||
| cgroup_hook.go | ||
| checks_hook.go | ||
| checks_hook_test.go | ||
| config.go | ||
| consul_grpc_sock_hook.go | ||
| consul_grpc_sock_hook_test.go | ||
| consul_http_sock_hook.go | ||
| consul_http_sock_hook_test.go | ||
| csi_hook.go | ||
| csi_hook_test.go | ||
| fail_hook.go | ||
| group_service_hook.go | ||
| group_service_hook_test.go | ||
| health_hook.go | ||
| health_hook_test.go | ||
| migrate_hook.go | ||
| network_hook.go | ||
| network_hook_test.go | ||
| network_manager_linux.go | ||
| network_manager_linux_test.go | ||
| network_manager_nonlinux.go | ||
| networking.go | ||
| networking_bridge_linux.go | ||
| networking_bridge_linux_test.go | ||
| networking_cni.go | ||
| networking_cni_test.go | ||
| testing.go | ||
| upstream_allocs_hook.go | ||