vendor: Revendor virtcontainers to 0.2.3 to fix a potential panic

Let's vendor virtcontainers 0.2.3, it's a good version if we want to minimize the changes while grabbing a fix for a panic that happens if the shim disappears underneath us. It's debatable if we should jump straight away to 0.3.0. That version would also need us to re-vender the runv package. It will have to happen, eventually, but we can control when. An benefit of going slowly on the updates is that we can revert a later vendoring to 0.3.0 if we find out it introduces regressions. Fixes: #463 Signed-off-by: Damien Lespiau <[email protected]>
intel · Jan 19, 2017 · 820e74b · 820e74b
1 parent 60fb0ac
commit 820e74b
Show file tree

Hide file tree

Showing 4 changed files with 109 additions and 94 deletions.
diff --git a/packages.json b/packages.json
@@ -21,7 +21,7 @@
 	},
 	"github.com/containers/virtcontainers": {
 		"url": "https://github.com/containers/virtcontainers.git",
-		"version": "v0.2.1",
+		"version": "v0.2.3",
 		"license": "Apache 2.0"
 	},
 	"github.com/stretchr/testify": {

diff --git a/vendor/github.com/containers/virtcontainers/README.md b/vendor/github.com/containers/virtcontainers/README.md
diff --git a/vendor/github.com/containers/virtcontainers/hyperstart/hyperstart.go b/vendor/github.com/containers/virtcontainers/hyperstart/hyperstart.go
diff --git a/vendor/github.com/containers/virtcontainers/hyperstart/mock/hyperstart.go b/vendor/github.com/containers/virtcontainers/hyperstart/mock/hyperstart.go