podman-search(1)
π podman-search(1) π
hii bestie, welcome to the podman-search(1) page from the General Commands Manual π it's short, it's sweet, it finds images for you, and by the end of this you're gonna be searching registries like it's nothing. let's go π¦
β¨ NAME β¨
podman-search β search a registry for an image π
πΈ SYNOPSIS πΈ
podman search [options] term
π DESCRIPTION π
okay so podman search goes and searches a registry β or a whole list of registries β for an image that matches what you're looking for. and the way you tell it which registry you want? you just prefix the registry right into the search term, like registry.fedoraproject.org/fedora β¨ easy. if you don't do that, it uses all the unqualified-search registries listed in containers-registries.conf(5) by default.
the default number of results is 25 β iconic number β and you can limit it with the --limit flag. heads up though: if more than one registry is being searched, that limit gets applied to each registry, not to the grand total. you can also filter the output with the --filter flag. and if you want everything available in a registry with no specific search term at all, just type the registry name with a trailing / and vibe β like registry.fedoraproject.org/ π«Ά
now for the real talk, bestie: podman search is NOT a reliable way to determine the presence or existence of an image. the search behavior of the v1 and v2 Docker distribution API is specific to the implementation of each registry, so it's giving "every registry does its own thing." some registries may not support searching at all π and searching without a search term only works for registries that implement the v2 API. no cap.
also, here are the invocation shapes you'll see floating around:
podman [GLOBAL OPTIONS]
podman search [GLOBAL OPTIONS]
podman search [OPTIONS] TERM
π OPTIONS π
--authfile=pathβ the path to the authentication file. default is${XDG_RUNTIME_DIR}/containers/auth.jsonon Linux, and$HOME/.config/containers/auth.jsonon Windows/macOS. this file is created bypodman login. and if the authorization state isn't found there, it checks$HOME/.docker/config.json, which is set usingdocker loginπ
also note: you can override the default path of the authentication file by setting the REGISTRY_AUTH_FILE environment variable. do it like this: export REGISTRY_AUTH_FILE=path.
--cert-dir=pathβ use the certificates at path (*.crt,*.cert,*.key) to connect to the registry. (default:/etc/containers/certs.d) for the deets, seecontainers-certs.d(5). β οΈ heads up: this option is not available with the remote Podman client, including Mac and Windows machines (excluding WSL2 ones).--compatibleβ after the name and the description, it also shows the stars, official and automated descriptors, exactly the way Docker does. Podman doesn't show these by default because most public container registries just don't support them π--creds=[username[:password]]β the[username[:password]]to use to authenticate with the registry, if required. if one or both values aren't supplied, a command line prompt pops up and you can enter the value. the password is entered without echo π€«
note that the credentials you specify are only used to authenticate against target registries. they are not used for mirrors or when the registry gets rewritten (see containers-registries.conf(5)) β for those, consider using a containers-auth.json(5) file instead.
--filter,-f=filter β filter the output based on conditions provided (default[])
supported filters are:
stars(int) β minimum number of stars required for images to showis-automated(boolean -true|false) β is the image automated or notis-official(boolean -true|false) β is the image official or not
--format=format β change the output format to a Go template
valid placeholders for the Go template are listed below:
.Automatedβ"[OK]"if image is automated.Descriptionβ image description.Indexβ registry.Nameβ image name.Officialβ"[OK]"if image is official.Starsβ star count of image.Tagβ repository tag
note: use .Tag only if the --list-tags is set.
--help,-hβ print usage statement--limit=limit β limit the number of results (default 25). note: the results from each registry is limited to this value. example: if limit is 10 and two registries are being searched, the total number of results is 20 β 10 from each (if there are at least 10 matches in each). the order of the search results is the order in which the API endpoint returns the results.--list-tagsβ list the available tags in the repository for the specified image. note:--list-tagsrequires the search term to be a fully specified image name. the result contains the image name and its tag, one line for every tag associated with the image π·οΈ--no-truncβ do not truncate the output (defaultfalse).--tls-verifyβ require HTTPS and verify certificates when contacting registries (default:true). if explicitly set totrue, TLS verification is used. if set tofalse, TLS verification is not used. if not specified, TLS verification is used unless the target registry is listed as an insecure registry incontainers-registries.conf(5).
π₯ EXAMPLES π₯
search for images containing the specified name, returning the first three images from each defined registry:
$ podman search --limit 3 fedora
NAME DESCRIPTION
registry.fedoraproject.org/f29/fedora-toolbox
registry.fedoraproject.org/f30/fedora-toolbox
registry.fedoraproject.org/f31/fedora-toolbox
docker.io/library/fedora Official Docker builds of Fedora
docker.io/kasmweb/fedora-37-desktop Fedora 37 desktop for Kasm Workspaces
docker.io/kasmweb/fedora-38-desktop Fedora 38 desktop for Kasm Workspaces
quay.io/fedora/fedora
quay.io/containerdisks/fedora # Fedora Containerdisk Images <img src="htt...
quay.io/fedora/fedora-minimal
note that the Stars, Official and Automated descriptors are only available on Docker Hub and are hence not displayed by default π
$ podman search --format "{{.Name}}\t{{.Stars}}\t{{.Official}}" alpine --limit 3
docker.io/library/alpine 7956 [OK]
docker.io/alpine/git 192
docker.io/anapsix/alpine-java 474
quay.io/libpod/alpine 0
quay.io/vqcomms/alpine-tools 0
quay.io/wire/alpine-deps 0
search and list tags for the specified image, returning the first four images from each defined registry:
$ podman search --list-tags registry.access.redhat.com/ubi8 --limit 4
NAME TAG
registry.access.redhat.com/ubi8 8.4-211
registry.access.redhat.com/ubi8 8.4-206.1626828523-source
registry.access.redhat.com/ubi8 8.4-199
registry.access.redhat.com/ubi8 8.4-211-source
note: this works only with registries that implement the v2 API. if you try it with a v1 registry, an error is returned π
π FILES π
registries.conf(/etc/containers/registries.conf)
registries.conf is the configuration file which specifies which container registries is consulted when completing image names which do not include a registry or domain portion ποΈ
π¦ SEE ALSO π¦
podman(1), containers-registries(5)
π HISTORY π
January 2018, originally compiled by Urvashi Mohnani umohnani@redhat.com <mailto:umohnani@redhat.com> π
and that's the whole page bestie, you ate that π«Ά this was podman-search(1) from the General Commands Manual, and if you ever need to find it again it's filed under that exact same name, periodt π
β¨π
π¦ where this page comes from
- arch rolling: podman-docker 6.1.4-1 Β· Apache-2.0
- fedora 43: podman-docker 5:5.6.2-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 43: podman-docker 5:5.8.4-1.fc43
- fedora 43: podman-docker 5:5.8.8-1.fc43
- fedora 43: podman-docker 5:5.8.9-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 44: podman-docker 5:5.8.1-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 44: podman-docker 5:5.8.7-1.fc44
- fedora 44: podman-docker 5:5.8.9-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- ubuntu resolute: podman-docker 5.7.0+ds2-3build1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms