浏览代码

Merge pull request #17180 from rhatdan/destroy

Docker is calling cont.Destroy twice on success
Brian Goff 9 年之前
父节点
当前提交
5087e8c2e8
共有 1 个文件被更改,包括 5 次插入1 次删除
  1. 5 1
      daemon/execdriver/native/driver.go

+ 5 - 1
daemon/execdriver/native/driver.go

@@ -132,6 +132,7 @@ type execOutput struct {
 // Run implements the exec driver Driver interface,
 // it calls libcontainer APIs to run a container.
 func (d *Driver) Run(c *execdriver.Command, pipes *execdriver.Pipes, hooks execdriver.Hooks) (execdriver.ExitStatus, error) {
+	destroyed := false
 	// take the Command and populate the libcontainer.Config from it
 	container, err := d.createContainer(c, hooks)
 	if err != nil {
@@ -157,7 +158,9 @@ func (d *Driver) Run(c *execdriver.Command, pipes *execdriver.Pipes, hooks execd
 	d.activeContainers[c.ID] = cont
 	d.Unlock()
 	defer func() {
-		cont.Destroy()
+		if !destroyed {
+			cont.Destroy()
+		}
 		d.cleanContainer(c.ID)
 	}()
 
@@ -191,6 +194,7 @@ func (d *Driver) Run(c *execdriver.Command, pipes *execdriver.Pipes, hooks execd
 		ps = execErr.ProcessState
 	}
 	cont.Destroy()
+	destroyed = true
 	_, oomKill := <-oom
 	return execdriver.ExitStatus{ExitCode: utils.ExitStatus(ps.Sys().(syscall.WaitStatus)), OOMKilled: oomKill}, nil
 }