Same software, but upstream changed the packaging.

And make sure to install cnitool, not noop (!)

See also https://falco.org/docs/installation/

Using podman-remote requires "varlink bridge"

Need a later version than the one provided by crio.

So use separate installations, one for each program.

Signed-off-by: NZhongcheng Lao <Zhongcheng.Lao@microsoft.com>

Signed-off-by: NZhongcheng Lao <Zhongcheng.Lao@microsoft.com>

Signed-off-by: NZhongcheng Lao <Zhongcheng.Lao@microsoft.com>

It has not been updated since kubernetes 1.9 or so

Since we already install docker and cni from binary

Signed-off-by: Nyanxuean <yan.xuean@zte.com.cn>

Simple management tool for containers and images

"podman shares state with crio and so has the
capability to debug pods/images created by crio"

https://github.com/projectatomic/libpod/pull/145

vboxguest is included in 4.16, but not vboxsf.
I couldn't get vboxsf to compile for 4.16, so I downgraded to 4.15.

This change adds gluster and heketi dependencies to buildroot config,
that is dm_snapshot, dm_thin_pool and XFS kernel modules, XFS tools,
and gluster itself.

linux is upgraded to 4.16, binutils is upgraded to 2.30, and
libelf is installed for the newer kernel.

Other configuration changes are changes in defaults and ordering.

Now using glibc 2.27. systemd 237, and Go 1.10.

vbox-guest is removed because it's upstream as of linux 4.16.

More on buildroot at https://git.buildroot.net/buildroot/tree/CHANGES

We don't need critest, because it requires go anyway.
But kubeadm insists on crictl being available in path.

buildroot's version is now more recent than the forked package.

https://github.com/kubernetes-incubator/cri-o

Updated the runc version to its latest master commit.
Got crio into the automounter to get off the tmpfs

This feature bubbles up to the minikube command by reusing the
`--container-runtime=` flag, by enabling the value of "`crio`"
(`minikube start --container-runtime=crio`), while the flags/config
passed to localkube are more like k8s (`--container-runtime=remote
--remote-runtime-endpoint=/var/run/crio.sock`)

This is mostly ready for review. It is still lacking having
--insecure-registry plumbed through, but for now the policy.json is
open.
Signed-off-by: NVincent Batts <vbatts@hashbangbash.com>

Also adds the cni-plugins-bin package, since they have been split out
into their own repo as of v0.6.0-rc1.

This rebases minikube-iso to the release 2017-02.

A change in buildroot required the introduction of a `external.desc` as
multiple external trees are supported in modern buildroot versions. This
required change is described here [0].

[0] https://buildroot.org/downloads/manual/manual.html#br2-external-converting

The existing isolinux.cfg was not included in the config and thus
ignored, include it.

The 4.9.13 kernel included in buildroot 2017-02 is not compatible with
VBox guest additions 5.1.6, thus bump guest additions to 5.1.18.

The defconfig of 4.9.13 has been cleaned up.

systemd 232 included in buildroot 2017-02 is incompatible with docker <
17.03 without boot parameter systemd.legacy_systemd_cgroup_controller=yes
Signed-off-by: NThomas Graf <tgraf@suug.ch>