-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kicbase build: E: Version '1.18.3~2' for 'cri-o' was not found #8982
Comments
There is a cri-o_1.18.3~3 now |
it might worth removing cri-o from supported and tested runtimes from minikube, since we don't have bandwith to troubleshoot cri-o packaing problems anymore. I created issues on cri-o package, I think once cri-o can provide stable packaging we can added it back to supported runtimes. |
The problem was that you tried to pin the package version (something that doesn't work - without a custom package repository)
Problem is "=1.18.3~2", it is the same issue as in Upstream only said to pin the package repository, to the wanted subproject - they created one for each branch and major release:
https://build.opensuse.org/project/subprojects/devel:kubic:libcontainers:stable But other than that, I tend to agree with the cost of supporting podman and cri-o (in addition to docker and docker)... It's just that it is "the new rkt", so without it we don't have any diversity and no testing of CRI and maybe not even CNI ? |
It seems that it is not currently possible to rebuild the kicbase image:
See https://github.com/kubernetes/minikube/pull/8974/checks?check_run_id=973059157
The text was updated successfully, but these errors were encountered: