Supply package cache for minikube container runtimes

[afbjorklund]

Since we can't rely on the vendor packages being available, we should make sure to host our own package cache ?

• https://kubernetes.io/docs/setup/production-environment/container-runtimes/

This would mostly include the container runtimes, but also other packages we install that are not in the distribution.

• Docker (docker.com, https://docs.docker.com/engine/install/ | https://github.com/docker/docker-ce)

  • docker-ce
  • docker-ce-client
  • containerd.io

• Podman (opensuse.org, https://build.opensuse.org/project/show/devel:kubic:libcontainers:stable)

  • podman
  • cri-o
  • conmon

• CRI

  • cri-tools

• CNI

  • plugins

There are distribution packages available for docker/containerd/runc, but we're not happy about the versions...

Currently using a personal package account on bintray.io (for podman and crio), but that is not maintainable...

• https://bintray.com/afbjorklund/podman/ (1.9.3)

• https://bintray.com/afbjorklund/cri-o/ (1.18.2)

We probably also need to document and automate the packaging building better, currenly using pbuilder.

For the Docker packages we don't know if we can build them from source code at all (that would be Moby)

Compare #6432 (comment)

[afbjorklund]

@medyagh

Most users would consume these using the images we provide (KIC and ISO), but it is important for the project.

There is a similar discussion for buildroot, but it doesn't have packages so it is mostly about static binaries there.

[afbjorklund]

I'm assuming here that minikube doesn't want a separate package/binary cache for the kubernetes components.

https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#installing-kubeadm-kubelet-and-kubectl

(or for our own)

[afbjorklund]

Once the upgrades to podman 2.1.1 and cri-o 1.18.4 are complete, the current package rebuilds are no longer needed...

• podman_1.9.3~1_amd64.deb
• cri-o_1.18.2~1_amd64.deb

But we should still save a cache, before they are deleted. Otherwise we would have to rebuild them again, in the future ?

• podman_2.1.1~2_amd64.deb (15.9 MB)
• cri-o_1.18.4~1_amd64.deb (19.9 MB)

https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman

https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable:cri-o:1.18/cri-o

[afbjorklund]

Added "buildkit" to the list, it doesn't seem to be available as a package (only as a pre-built binary)

• buildkit_0.7.2-1_amd64.deb

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

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

[medyagh]

this seems like a good idea, our current release is blocked by both crio and podman again since we cant install their packages cri-o/cri-o#5343

[lsm5]

check if cri-o/cri-o#5343 (comment) helps.

[afbjorklund]

New errors, from yesterday:

#190 15.73 Err:2 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.22/xUbuntu_20.04  cri-o 1.22.1~1
#190 15.73   File has unexpected size (20117236 != 20117924). Mirror sync in progress? [IP: 91.193.113.70 443]
#190 15.73   Hashes of expected file:
#190 15.73    - SHA256:8bd675437e2ca9eb9873ff22cc3dfc90cc67a55620923a799929f6e1597201e3
#190 15.73    - SHA1:3725c9c349b420edd2a03e071926b8a01c3144a9 [weak]
#190 15.73    - MD5Sum:ae6cf72fecfa5ff031450dd075526720 [weak]
#190 15.73    - Filesize:20117924 [weak]