Improve the default crio-bin configuration

[afbjorklund]

Cherry-picked some of the podman changes, since they are really for crio-bin. (#2757)

• use the standard directory and a bind-mount, instead of a prefixed storage directory

• add the standard docker registry, so that you can run/pull images (like e.g. busybox)

We also need the crictl.yaml fixes, but that needs to be versioned on the CRI (#3043)

[afbjorklund]

Possibly the standard registry should be merged with the /etc/sysconfig/crio.minikube ?

https://github.com/kubernetes/minikube/blob/master/pkg/provision/buildroot.go#L188:L215

That already sets the --insecure-registry

[afbjorklund]

Tried to use a well-defined storage provisioner, so that it can be used by crictl and podman too...

But Jenkins didn't like it, for some reason.

[tstromberg]

@afbjorklund - Any idea what the OSX-Hyperkit errors are all about? They seem like a flake, but one I haven't seen yet:

• FAIL: TestFunctional/Mounting (230.50s)
  util.go:303: Error: open /var/folders/pb/1pdf6kyd1n9fw671gj2162wr0000gp/T/mounttest682921312/frompod: no such file or directory, Retrying in 5s. 40 Retries remaining.

[tstromberg]

@minikube-bot OK to test

[afbjorklund]

@tstromberg : have only tried libvirt (kvm2), sorry

[afbjorklund]

Also fixes issue #2835 (registries missing)

[tstromberg]

@minikube-bot OK to test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afbjorklund, tstromberg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tstromberg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment