-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
podman search does not return results unless registry specified #8896
Comments
Thanks for reaching out! # /etc/containers/registries.conf
[[registry]]
location = "docker.io"
[[registry]]
location = "registry.fedoraproject.org"
[[registry]]
location = "registry.access.redhat.com" The upper config isn't correct. You need to set it as follows: unqualified-search-registries=["registry.access.redhat.com", "registry.fedoraproject.org", "docker.io"] |
Wow, thanks, it works now. But that was not at all obvious to me... I have reread the comments in the default |
I admit that the config can be quite complex. If you have suggestions to make it easer to digest, feel free to share. Any feedback is helpful :) |
Why 'unqualified-search-registries'? It's also not advertised as such in the podman.io documentation which shows general searches. https://podman.io/getting-started/ |
Agreed, the examples in the documentation should work with the default config. |
Which default config (on which distribution) are you referring to? |
The search registries are mentioned in the first paragraph. If you have concrete suggestions to improve the docs, please let me know. |
Hi, I'm the one who is completely new to containers ( https://docs.podman.io/en/latest/ ) , and it gives a link to "https://docs.podman.io/en/latest/Introduction.html" , follow the post and get empty result. why not give a link to tutorials ? |
Why are you posting on this issue? Documentation issues with |
Can confirm that this is still frustrating for a new user who's trying to follow the docs:
But all I really want is a clear "Here, put THIS in your config to get started" rather than |
Does Arch not set any unqualified-search-registry in /etc/containers/registries.conf? |
Nope, no lines in the config from containers-common were uncommented, so not just was there no unqaulified-search-registry, there weren't any registries defined at all. At any rate, I was just trying to get rootless mode up and running, so putting the following into unqualified-search-registries = ["docker.io"]
[[registry]]
location = "docker.io" |
Thanks for confirming, @jcorbin! I suggest reaching out to the Arch maintainers. |
prefixing the registry name works, even if docker.io is not specified as the registry in the configuration file like: ``` unqualified-search-registries = ["docker.io"] [[registry]] location = "docker.io" ``` containers#8896 Signed-off-by: gubbu <38842604+gubbu@users.noreply.github.com>
The podman.io repo received a new PR a day or two ago about this discussion/issue. Pasting the comment here for @rkiddy Text from the Podman.io PR 262 : Otherwise, to a neophyte user, the 'podman search' command returns nothing and seems broken. See #8896 But why should it be necessary to find the issue. The suggestion in the bug was good. So, why not just throw a bone to the new user? |
/kind bug
Description
Running
podman search
returns nothing, even though three registries are configured.Steps to reproduce the issue:
/etc/containers/registries.conf
inVERSION 2
format:Search on a specific repository to verify that it can actually find something:
Describe the results you received:
Empty result
Describe the results you expected:
Search results from all configured registries.
Additional information you deem important (e.g. issue happens only occasionally):
Podman is running rootless using cgroups v2.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical machine running latest kernel:
The text was updated successfully, but these errors were encountered: