summaryrefslogtreecommitdiffstats
path: root/recipes-networking/cni
diff options
context:
space:
mode:
authorMark Asselstine <mark.asselstine@windriver.com>2020-03-06 16:54:08 -0500
committerBruce Ashfield <bruce.ashfield@gmail.com>2020-03-13 21:53:26 -0400
commit685d518eb75f02ddd8f4ca7a7d35b72d924f5487 (patch)
tree30486b2534e3606fa68811ebf496e963995fa83b /recipes-networking/cni
parente57cf80d54ad929db7e4e677fbbd9e5a3dee22fe (diff)
downloadmeta-virtualization-685d518eb75f02ddd8f4ca7a7d35b72d924f5487.tar.gz
cri-o: uprev from 1.15 to 1.17
Uprev to the latest release of cri-o to pick up some fixes and CVEs. Makefile updates along with updates to the go.bbclass allow us to remove most of the do_compile() tweaks that were in place. To test that these removals are sane builds were done for x86_64 and arm64 in docker containers with network=none, no issues were found. Quite a few runtime tests were done as well since we are stepping up 2 releases, and we also just uprev'd 'cni' and wanted to validate its runtime as well. Once the system is started and cri-o is given time to start you can use the new 'crio-status info' command to retrieve the runtime status of cri-o: root@qemux86-64:~# crio-status info cgroup driver: cgroupfs storage driver: storage root: /var/lib/containers/storage default GID mappings (format <container>:<host>:<size>): 0:0:4294967295 default UID mappings (format <container>:<host>:<size>): 0:0:4294967295 Additionally 'crictl' was installed (the recipe will be submitted shortly) and the cri-o Tutorial found here was run (https://github.com/cri-o/cri-o/blob/master/tutorials/crictl.md) In order to run the tutorial /etc/cni/net.d/99-loopback.conf and /etc/containers/policy.json were taken from ./contrib/cni/99-loopback.conf and ./contrib/policy.json in the cri-o src repo. The sandbox_config.json and container_redis.json were taken from https://github.com/cri-o/cri-o/blob/master/test/testdata (note: using core-image-minimal with systemd enabled I had to remove "cpu_period": 10000 and "cpu_quota": 20000 to get the tutorial to work). We are not able to use the loopback networking to telnet to the redis container, but we can use other techniques to validate that it is running. root@qemux86-64:~# /usr/lib/go/src/import/_output/crictl --runtime-endpoint unix:///var/run/crio/crio.sock ps CONTAINER IMAGE CREATED STATE NAME ATTEMPT POD ID 72718714360ef quay.io/crio/redis:alpine 47 seconds ago Running podsandbox1-redis 0 38b97e5a7bb99 root@qemux86-64:~# /usr/lib/go/src/import/_output/crictl --runtime-endpoint unix:///var/run/crio/crio.sock exec -i 72718714360ef cat /etc/issue Welcome to Alpine Linux 3.7 Kernel \r on an \m (\l) The CRIO_BUILD_CROSS approach was no longer valid and was dropped. There is most likely some other cleanup we can do but this gets us to a good state on the latest release. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'recipes-networking/cni')
0 files changed, 0 insertions, 0 deletions