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

UPSTREAM: 59301: dockershim: don't check pod IP in StopPodSandbox #18425

Merged
merged 1 commit into from
Mar 21, 2018

Commits on Feb 27, 2018

  1. UPSTREAM: 59301: dockershim: don't check pod IP in StopPodSandbox

    We're about to tear the container down, there's no point.  It also suppresses
    an annoying error message due to kubelet stupidity that causes multiple
    parallel calls to StopPodSandbox for the same sandbox.
    
    docker_sandbox.go:355] failed to read pod IP from plugin/docker: NetworkPlugin cni failed on the status hook for pod "docker-registry-1-deploy_default": Unexpected command output nsenter: cannot open /proc/22646/ns/net: No such file or directory
    
    1) A first StopPodSandbox() request triggered by SyncLoop(PLEG) for
    a ContainerDied event calls into TearDownPod() and thus the network
    plugin.  Until this completes, networkReady=true for the
    sandbox.
    
    2) A second StopPodSandbox() request triggered by SyncLoop(REMOVE)
    calls PodSandboxStatus() and calls into the network plugin to read
    the IP address because networkReady=true
    
    3) The first request exits the network plugin, sets networReady=false,
    and calls StopContainer() on the sandbox.  This destroys the network
    namespace.
    
    4) The second request finally gets around to running nsenter but
    the network namespace is already destroyed.  It returns an error
    which is logged by getIP().
    dcbw committed Feb 27, 2018
    Configuration menu
    Copy the full SHA
    acac9a8 View commit details
    Browse the repository at this point in the history