Skip to content

fully-qualifies example image, to support non-docker runtimes #524

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

Merged

Conversation

mhrivnak
Copy link
Member

Non-docker runtimes may not assume a particular registry. The CRI avoids such
assumptions, leaving it up to individual runtimes. CRI-O as one runtime example
does not assume docker.io.

This change can be tested with cri-o on minikube with a command similar to:

minikube start --kubernetes-version=v1.11.3 --network-plugin=cni --container-runtime=cri-o

Non-docker runtimes may not assume a particular registry. The CRI avoids such
assumptions, leaving it up to individual runtimes. CRI-O as one runtime example
does not assume docker.io.

This change can be tested with cri-o on minikube with a command similar to:

`minikube start --kubernetes-version=v1.11.3 --network-plugin=cni --container-runtime=cri-o`
@mhrivnak mhrivnak added the kind/bug Categorizes issue or PR as related to a bug. label Sep 24, 2018
@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 24, 2018
@hasbro17
Copy link
Contributor

LGTM
Good catch.

@hasbro17 hasbro17 merged commit 7f00ede into operator-framework:master Sep 24, 2018
@mhrivnak mhrivnak deleted the qualify-example-image-name branch September 24, 2018 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants