vendor: update dependency opencontainers/runc #588
This updates openconatainer/runc (and its deps). Ref. opencontainers/runc#2065, running a version before that fix will result in some strange behavior on Aarch64 (Linux 5.0.X+).
Also related to kata-containers/tests#1726, since because of the same problem (in k8s) kubelet, the node process, is unable to start on AArch64.
Runc diff here: opencontainers/runc@f56b4cb...f4982d8
3 times, most recently
Jun 22, 2019
@@ Coverage Diff @@ ## master #588 +/- ## ========================================== + Coverage 50.45% 50.62% +0.16% ========================================== Files 17 17 Lines 2392 2392 ========================================== + Hits 1207 1211 +4 + Misses 1028 1026 -2 + Partials 157 155 -2
Hi @odinuge - Thanks for raising! This looks good - the only thing left to do is to raise an issue and reference it in your commit with
Don't worry if the issue is not assigned to you (we don't appear to be able to massage GitHub into allowing new contributors to self-assign issues).
Interestingly, the CI checks didn't catch this since three of the re-vendor commits summarised in your commit message specify a