Add possibility to use host docker registry

[afbjorklund]

A lot of the startup time is transferring and unpacking the container images.

Either from the cache or from the preload, to be copied from host to the node.

It would be useful to be able to pull these from a registry running on the host...
https://docs.docker.com/registry/recipes/mirror/#run-a-registry-as-a-pull-through-cache

Such a registry server would also be an alternative instead of minikube image

The canonical server is docker distribution (registry v2): https://docs.docker.com/registry/

It is now in CNCF: https://www.docker.com/blog/donating-docker-distribution-to-the-cncf/

---

This would also allow for future optimizations, such as lazy pulling with stargz:

"Startup Containers in Lightning Speed with Lazy Image Distribution on Containerd"

By providing optimized images, it would allow the k8s cluster to start up faster.

The same goes for the apps, when their images stay resident in host memory.

[afbjorklund]

Compare https://kind.sigs.k8s.io/docs/user/local-registry/

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten