Upgrade software versions on the minikube ISO

[afbjorklund]

Tracker for some separate issues, regarding ISO:

• Upgrade Buildroot, from 2020.02 to 2021.02
  • 2020.02.12 (EOL)
  • 2021.02.4 (LTS)
• Upgrade Docker and other container runtimes
  • runc v1.0.1 ✓
  • containerd v1.4.9 ✓
  • docker 20.10.8 ✓
  • buildkit 0.9.0 ✓
  • (crun 0.20.1) (alternative to runc)
  • cri-o 1.20.3
  • podman 3.1.2
  • (buildah 1.20.1) (included in podman)

PRs: #11688 #12268 #11593 #12122 #11594 #12032 #11595 #11679 #11727

EDIT: PR #11688 was reverted in #11799 due to #11810

[afbjorklund]

We still don't fully know what the long term plan will be: #9992

But we will do one more major update to ISO, based on current

Release Notes

2021.02.3:
http://lists.busybox.net/pipermail/buildroot/2021-June/312591.html
2021.02.2:
http://lists.busybox.net/pipermail/buildroot/2021-May/310003.html
2021.02.1:
http://lists.busybox.net/pipermail/buildroot/2021-April/307970.html
2021.02:
http://lists.busybox.net/pipermail/buildroot/2021-March/305168.html

Notice that this is a long term support release which will be supported with security and other important fixes until March 2022.

There is a plan to offer a version with Linux 5.4, as an alternative.

[afbjorklund]

This issue is currently blocking the Linux 5 version and the ARM 64 version:

#11056 5.4

BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.19.194"
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.4.125"

#9228 arm64

BR2_x86_64=y
BR2_aarch64=y

Those would be add-ons/alternative versions building, from this updated ISO.

[afbjorklund]

The buildroot OS upgrade is being blocked by "cilium" issues with systemd: #11810

[afbjorklund]

2021.02.4:
http://lists.busybox.net/pipermail/buildroot/2021-August/620747.html

/etc/sysctl.d/90-cilium-rp_filter.conf

net.ipv4.conf.lxc*.rp_filter = 0
net.ipv4.conf.cilium_*.rp_filter = 0

[djgraff209]

Should this issue now be punted to milestone 1.24.0 since 1.23.0 went out with out it?

[afbjorklund]

Possibly wrong to add a "tracker" bug, most things except for podman/cri-o actually did make it...

[djgraff209]

Understood and thank you for your efforts.

Is there any clarity around an updated podman? I'm super interested in using this as a docker desktop replacement on windows and Mac.

All of the clients that are available are 3.3.0 or later which are not compatible with the 2.2.1 API version bundled.

Thank you again

[afbjorklund]

Podman is not fully supported for running containers with, it's more like a support tool to CRI-O (for loading and building)

So the main use is for minikube image, but I think that it still works OK as long as you install a podman2 separately...

https://github.com/containers/podman/releases/tag/v2.2.1

Unfortunately there are no pre-built binaries available for it.

There is no support for rootless containers though, so you have to run sudo podman (or use minikube podman-env)

If looking for a tool similar to Docker Machine/Podman Machine, I would currently recommend using Vagrant (until 4.0)

[afbjorklund]

There are a lot of "Podman Desktop" discussions elsewhere though, including a Podman Community meeting happening tomorrow.

https://podman.io/community/

But we might have to add a FAQ about Docker Desktop (and also Docker Engine), since it is the preferred minikube driver now...

7564651

[djgraff209]

I think my main focus was being able to do minikube + podman-env for the near term - heck even docker-env with the cli might suffice.

The one thing that was most appealing was the ability to use either hyperkit (macos) or hyper-v (windows 10 ent/pro). The virtualization options looked much cleaner in those respects.

Thanks again for providing alternatives to just docker desktop as well as a solid (simple) kubernetes environment.

[afbjorklund]

I think my main focus was being able to do minikube + podman-env for the near term - heck even docker-env with the cli might suffice.

Those features will remain for the foreseeable future, a bit of a pity with the lack of compatibilty between podman2 and podman3 (and soon it will break again with podman4!) and about the slow adoption of ssh: support in the docker client and libraries.

But right now it is mostly the containerd runtime that lacks a proper environment, due to shortcomings in the tools (but workarounds documented). It is not impossible to make a "minikube containerd-env", but it would also be nice not to have to...

I'm not sure how long Docker will continue to support machine and hyperkit*, so we might have to fork and include them.

* hyperkit is based on an open source project called xhyve, which in turn is based on Apple's system frameworks. So no worries.

[afbjorklund]

Closing this issue, due to that the OS and docker/containerd did make it (and nobody cares about podman/crio)