podman-manifest-push(1)

1podman-manifest-push(1)     General Commands Manual    podman-manifest-push(1)
2
3
4

NAME

6       podman-manifest-push  -  Push  a manifest list or image index to a reg‐
7       istry
8
9

SYNOPSIS

11       podman manifest push [options] listnameorindexname [destination]
12
13

DESCRIPTION

15       Pushes a manifest list or image index to a registry.
16
17

RETURN VALUE

19       The list image's ID and the digest of the image's manifest.
20
21

OPTIONS

23   --all
24       Push the images mentioned in the manifest list or image index, in addi‐
25       tion to the list or index itself. (Default true)
26
27
28   --authfile=path
29       Path of the authentication file. Default is ${XDG_RUNTIME_DIR}/contain‐
30       ers/auth.json, which is set using podman login.  If  the  authorization
31       state  is  not found there, $HOME/.docker/config.json is checked, which
32       is set using docker login.
33
34
35       Note: There is also the option to override the default path of the  au‐
36       thentication  file  by setting the REGISTRY_AUTH_FILE environment vari‐
37       able. This can be done with export REGISTRY_AUTH_FILE=path.
38
39
40   --cert-dir=path
41       Use certificates at path (*.crt, *.cert, *.key) to connect to the  reg‐
42       istry.  (Default:  /etc/containers/certs.d) Please refer to containers-
43       certs.d(5) for details.  (This option is not available with the  remote
44       Podman client, including Mac and Windows (excluding WSL2) machines)
45
46
47   --compression-format=gzip | zstd | zstd:chunked
48       Specifies  the  compression format to use.  Supported values are: gzip,
49       zstd and zstd:chunked.  The default is gzip unless  overridden  in  the
50       containers.conf file.
51
52
53   --creds=[username[:password]]
54       The  [username[:password]] to use to authenticate with the registry, if
55       required.  If one or both values  are  not  supplied,  a  command  line
56       prompt  will  appear  and the value can be entered. The password is en‐
57       tered without echo.
58
59
60   --digestfile=Digestfile
61       After copying the image, write the digest of the resulting image to the
62       file.  (This option is not available with the remote Podman client, in‐
63       cluding Mac and Windows (excluding WSL2) machines)
64
65
66   --format, -f=format
67       Manifest list type (oci or v2s2) to use when pushing the list  (default
68       is oci).
69
70
71   --quiet, -q
72       When writing the manifest, suppress progress output
73
74
75   --remove-signatures
76       Don't copy signatures when pushing images.
77
78
79   --rm
80       Delete  the  manifest list or image index from local storage if pushing
81       succeeds.
82
83
84   --sign-by=fingerprint
85       Sign the pushed images with a  “simple  signing”  signature  using  the
86       specified  key.  (This  option  is not available with the remote Podman
87       client, including Mac and Windows (excluding WSL2) machines)
88
89
90   --sign-by-sigstore-private-key=path
91       Sign the pushed images with a sigstore signature using a private key at
92       the  specified path. (This option is not available with the remote Pod‐
93       man client, including Mac and Windows (excluding WSL2) machines)
94
95
96   --sign-passphrase-file=path
97       If signing the image (using either --sign-by or --sign-by-sigstore-pri‐
98       vate-key), read the passphrase to use from the specified path.
99
100
101   --tls-verify
102       Require  HTTPS  and verify certificates when contacting registries (de‐
103       fault: true).  If explicitly set to  true,  TLS  verification  will  be
104       used.   If  set  to  false,  TLS verification will not be used.  If not
105       specified, TLS verification will be used unless the target registry  is
106       listed as an insecure registry in containers-registries.conf(5)
107
108

DESTINATION

110       The DESTINATION is a location to store container images
111        The Image "DESTINATION" uses a "transport":"details" format.
112        If a transport is not given, podman push will attempt to push
113        to a registry.
114
115
116       Multiple transports are supported:
117
118
119       dir:path
120         An existing local directory path storing the manifest, layer tarballs
121       and signatures as individual files. This is a non-standardized  format,
122       primarily useful for debugging or noninvasive container inspection.
123
124
125              $ podman manifest push mylist:v1.11 dir:/tmp/mylist
126
127
128
129       docker://docker-reference
130         An  image  in  a  registry implementing the "Docker Registry HTTP API
131       V2". By default, uses the authorization state in  $XDG_RUNTIME_DIR/con‐
132       tainers/auth.json, which is set using (podman login). If the authoriza‐
133       tion state is not found there,  $HOME/.docker/config.json  is  checked,
134       which is set using (docker login).
135
136
137              $ podman manifest push mylist:v1.11 docker://registry.example.org/mylist:v1.11
138
139
140
141       docker-archive:path[:docker-reference]
142         An  image is stored in the docker save formatted file.  docker-refer‐
143       ence is only used when creating such a file, and it must not contain  a
144       digest.
145
146
147              $ podman manifest push mylist:v1.11 docker-archive:/tmp/mylist
148
149
150
151       docker-daemon:docker-reference
152         An  image  in docker-reference format stored in the docker daemon in‐
153       ternal storage. docker-reference must contain a tag.
154
155
156              $ podman manifest push mylist:v1.11 docker-daemon:registry.example.org/mylist:v1.11
157
158
159
160       oci-archive:path:tag
161         An image tag in a directory compliant with "Open Container Image Lay‐
162       out Specification" at path.
163
164
165              $ podman manifest push mylist:v1.11 oci-archive:/tmp/mylist
166
167
168

EXAMPLE

170              podman manifest push mylist:v1.11 docker://registry.example.org/mylist:v1.11
171
172
173