Skip to content
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

add docker.io registry #63

Merged

Conversation

rphillips
Copy link
Contributor

Enables docker.io registries

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 14, 2018
@rphillips rphillips mentioned this pull request Sep 14, 2018
@abhinavdahiya
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 14, 2018
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, rphillips

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 14, 2018
@cgwalters
Copy link
Member

I'll just continue my quest against this by commenting here:

https://bugzilla.redhat.com/show_bug.cgi?id=1434897#c7
https://url.corp.redhat.com/walters-registry-equality

@cgwalters
Copy link
Member

(Why are we overriding the config files shipped in the RPMs anyways?)

@openshift-merge-robot openshift-merge-robot merged commit 16dbf47 into openshift:master Sep 14, 2018
@cgwalters
Copy link
Member

Oh...this is probably because cri-o doesn't search docker.io by default right?

If that's breaking our code, and we are actually intending to pull containers from docker.io, I think we should explicitly spell that out in the configs.

@rphillips
Copy link
Contributor Author

@cgwalters end users of containers usually expect docker pull busybox to pull the docker hub busybox.

@cgwalters
Copy link
Member

(The question of it affecting users is IMO distinct...probably we should have a high level config knob in the installer to affect the registry search order)

@cgwalters end users of containers usually expect docker pull busybox to pull the docker hub busybox.

Right, but we're not shipping /usr/bin/docker.

@sjenning
Copy link
Contributor

sjenning commented Sep 14, 2018

Oh...this is probably because cri-o doesn't search docker.io by default right?
If that's breaking our code, and we are actually intending to pull containers from docker.io, I think we should explicitly spell that out in the configs.

Completely agree and we are working to find all those places. We know the router, registry, and webconsole currently do not fully qualify their image paths.

Ideally we get to a world where the search list is empty and everyone fully qualifies their image paths.

@sjenning
Copy link
Contributor

sjenning commented Sep 14, 2018

osherdp pushed a commit to osherdp/machine-config-operator that referenced this pull request Apr 13, 2021
remove configmap and move its contents into SamplesResource.Status
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants