.nh .TH podman-search 1 .SH NAME .PP podman-search - Search a registry for an image .SH SYNOPSIS .PP \fBpodman search\fP [\fIoptions\fP] \fIterm\fP .SH DESCRIPTION .PP \fBpodman search\fP searches a registry or a list of registries for a matching image. The user can specify which registry to search by prefixing the registry in the search term (e.g., \fBregistry.fedoraproject.org/fedora\fP). By default, all unqualified-search registries in \fB\fCcontainers-registries.conf(5)\fR are used. .PP The default number of results is 25. The number of results can be limited using the \fB--limit\fP flag. If more than one registry is being searched, the limit will be applied to each registry. The output can be filtered using the \fB--filter\fP flag. To get all available images in a registry without a specific search term, the user can just enter the registry name with a trailing "/" (example \fBregistry.fedoraproject.org/\fP). .PP Note that \fBpodman search\fP 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. Some registries may not support searching at all. Further note that searching without a search term will only work for registries that implement the v2 API. .PP \fBpodman [GLOBAL OPTIONS]\fP .PP \fBpodman search [GLOBAL OPTIONS]\fP .PP \fBpodman search [OPTIONS] TERM\fP .SH OPTIONS .SS \fB--authfile\fP=\fIpath\fP .PP Path of the authentication file. Default is \fB\fC${XDG_RUNTIME_DIR}/containers/auth.json\fR, which is set using \fBpodman login\fP\&. If the authorization state is not found there, \fB\fC$HOME/.docker/config.json\fR is checked, which is set using \fBdocker login\fP\&. .PP Note: There is also the option to override the default path of the authentication file by setting the \fB\fCREGISTRY_AUTH_FILE\fR environment variable. This can be done with \fBexport REGISTRY_AUTH_FILE=\fIpath\fP\fP\&. .SS \fB--compatible\fP .PP After the name and the description, also show the stars, official and automated descriptors as Docker does. Podman does not show these descriptors by default since they are not supported by most public container registries. .SS \fB--filter\fP, \fB-f\fP=\fIfilter\fP .PP Filter output based on conditions provided (default []) .PP Supported filters are: .RS .IP \(bu 2 stars (int - number of stars the image has) .IP \(bu 2 is-automated (boolean - true | false) - is the image automated or not .IP \(bu 2 is-official (boolean - true | false) - is the image official or not .RE .SS \fB--format\fP=\fIformat\fP .PP Change the output format to a Go template .PP Valid placeholders for the Go template are listed below: .TS allbox; l l l l . \fB\fC\fBPlaceholder\fP\fR \fB\fC\fBDescription\fP\fR \&.Index Registry \&.Name Image name \&.Description Image description \&.Stars Star count of image \&.Official "[OK]" if image is official \&.Automated "[OK]" if image is automated \&.Tag Repository tag .TE .PP Note: use .Tag only if the --list-tags is set. .SS \fB--help\fP, \fB-h\fP .PP Print usage statement .SS \fB--limit\fP=\fIlimit\fP .PP Limit the number of results (default 25). Note: The results from each registry will be limited to this value. Example if limit is 10 and two registries are being searched, the total number of results will be 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. .SS \fB--list-tags\fP .PP List the available tags in the repository for the specified image. \fBNote:\fP --list-tags requires 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. .SS \fB--no-trunc\fP .PP Do not truncate the output (default \fIfalse\fP). .SS \fB--tls-verify\fP .PP Require HTTPS and verify certificates when contacting registries (default: \fBtrue\fP). If explicitly set to \fBtrue\fP, TLS verification will be used. If set to \fBfalse\fP, TLS verification will not be used. If not specified, TLS verification will be used unless the target registry is listed as an insecure registry in \fBcontainers-registries.conf(5)\fP .SH EXAMPLES .PP .RS .nf $ podman search --limit 3 fedora NAME DESCRIPTION registry.centos.org/centos registry.centos.org/cdrage/mosh-centos7 registry.centos.org/centos/bind docker.io/library/centos The official build of CentOS. docker.io/jdeathe/centos-ssh OpenSSH / Supervisor / EPEL/IUS/SCL Repos - ... docker.io/ansible/centos7-ansible Ansible on Centos7 quay.io/centos/centos The official CentOS base containers. quay.io/ukhomeofficedigital/centos-base quay.io/quarkus/centos-quarkus-maven Quarkus.io builder image for building Quarku... .fi .RE .PP Note that the Stars, Official and Automated descriptors are only available on Docker Hub and are hence not displayed by default. .PP .RS .nf $ 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 .fi .RE .PP .RS .nf $ 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 .fi .RE .PP Note: This works only with registries that implement the v2 API. If tried with a v1 registry an error will be returned. .SH FILES .PP \fBregistries.conf\fP (\fB\fC/etc/containers/registries.conf\fR) .PP registries.conf is the configuration file which specifies which container registries should be consulted when completing image names which do not include a registry or domain portion. .SH SEE ALSO .PP \fBpodman(1)\fP, \fBcontainers-registries(5)\fP .SH HISTORY .PP January 2018, Originally compiled by Urvashi Mohnani umohnani@redhat.com \[la]mailto:umohnani@redhat.com\[ra]