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

containers.conf: add option to enforce docker.io for compat API #833

Merged
merged 1 commit into from
Nov 22, 2021

Conversation

vrothberg
Copy link
Member

Add an option to containers.conf as a knob to enforce short-name
resolution to Docker Hub in Podman's compatibility REST API.

By popular request, turn it on by default.

Signed-off-by: Valentin Rothberg [email protected]

@rhatdan @mtrmac PTAL

Add an option to containers.conf as a knob to enforce short-name
resolution to Docker Hub in Podman's compatibility REST API.

By popular request, turn it on by default.

Signed-off-by: Valentin Rothberg <[email protected]>
Copy link
Contributor

@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Conceptually this is the wrong granularity, because whether unqualified names are short and should trigger search, or shorthands for docker.io, is a property of an individual API client, not of the whole OS.

But, *shrug*, up to Podman to define what its API means now.

@vrothberg
Copy link
Member Author

vrothberg commented Nov 22, 2021

@rhatdan wanted a knob in containers.conf. While it's a global config, there are a number of otpions that are podman-specific already. I made sure in the description to limit the effect to Podman's compat REST API.

@mtrmac
Copy link
Contributor

mtrmac commented Nov 22, 2021

For the record, by “API client” I didn’t mean Podman; I meant things like the Kubelet, /usr/bin/docker (a _specific version of it, actually), and the like — things talking over the AF_UNIX socket. Any one of them can want short names to be interpreted differently (depending specific version that might or might not have a client change necessary to interoperate with projectatomic/docker) — or just as likely, they might be completely unaware of the issue and “just passing user input to a library”.

@vrothberg
Copy link
Member Author

Thanks for elaborating. Yes, some users would always have to change something/some config. Having this option allows at least to change the behavior. Hard-coding it for the compat API without opting out was something I strongly opposed.

@mtrmac
Copy link
Contributor

mtrmac commented Nov 22, 2021

That’s fair. Nowadays, with the single-purpose VM proliferation, a per-system option might be good enough.

@rhatdan
Copy link
Member

rhatdan commented Nov 22, 2021

/approve
/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhatdan, vrothberg

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-merge-robot openshift-merge-robot merged commit 66fcfe2 into containers:main Nov 22, 2021
@vrothberg vrothberg deleted the compat-registry branch November 23, 2021 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants