Prototype buildroot in kicbase

[medyagh]

the current pain point is maintaing two operating systems
one for VM
and one for Kicbase
kic base here https://github.com/kubernetes/minikube/tree/master/deploy/kicbase
and iso here https://github.com/kubernetes/minikube/tree/master/deploy/iso
one idea would be moving ISO to ubuntu
but that would make ISO much bigger
or we could change docker to be buildroot

[medyagh]

@afbjorklund had a working PR that we didnt continue long time ago, it woudl be nice to re-do it and see the metrics

[afbjorklund]

The prototype was done here: #6942 The other alternative (standard distribution) is here: #9992

[afbjorklund]

The kicbase image is based on kind, while the buildroot image is based on coreos

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[afbjorklund]

/remove-lifecycle stale

[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

[sharifelgamal]

@medyagh do we still care about this?