ci: Remove workaround to test 'cri-o' in GH actions #1945
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was an issue running minikube with --container-runtime=cri-o in GitHub actions due to docker version older than v0.23.0 kubernetes/minikube#12928 (comment). Signed-off-by: Qasim Sarfraz <qasimsarfraz@microsoft.com>
mqasimsarfraz
force-pushed
the
qasim/remove-crio-workaround
branch
from
9192eda
to
8fe8199
Compare
eiffel-fl
approved these changes
Aug 8, 2023
|
Thanks for the review! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was an issue running
minikubewith--container-runtime=cri-oin GitHub actions due to docker version older thanv0.23.0kubernetes/minikube#12928 (comment). GitHub actions now use newer version so it should be fine to remove the workaround.