1podman-manifest-add(1) General Commands Manual podman-manifest-add(1)
2
3
4
6 podman-manifest-add - Add an image to a manifest list or image index
7
8
10 podman manifest add [options] listnameorindexname [transport]:imagename
11
12
14 Adds the specified image to the specified manifest list or image index.
15
16
18 The list image's ID.
19
20
22 --all
23 If the image which is added to the list or index is itself a list or
24 index, add all of the contents to the local list. By default, only one
25 image from such a list or index is added to the list or index. Combin‐
26 ing --all with any of the other options described below is NOT recom‐
27 mended.
28
29
30 --annotation=annotation=value
31 Set an annotation on the entry for the image.
32
33
34 --arch
35 Override the architecture which the list or index records as a require‐
36 ment for the image. If imageName refers to a manifest list or image
37 index, the architecture information is retrieved from it. Otherwise,
38 it is retrieved from the image's configuration information.
39
40
41 --authfile=path
42 Path of the authentication file. Default is ${XDG_RUNTIME_DIR}/contain‐
43 ers/auth.json on Linux, and $HOME/.config/containers/auth.json on Win‐
44 dows/macOS. The file is created by podman login. If the authorization
45 state is not found there, $HOME/.docker/config.json is checked, which
46 is set using docker login.
47
48
49 Note: There is also the option to override the default path of the au‐
50 thentication file by setting the REGISTRY_AUTH_FILE environment vari‐
51 able. This can be done with export REGISTRY_AUTH_FILE=path.
52
53
54 --cert-dir=path
55 Use certificates at path (*.crt, *.cert, *.key) to connect to the reg‐
56 istry. (Default: /etc/containers/certs.d) For details, see containers-
57 certs.d(5). (This option is not available with the remote Podman
58 client, including Mac and Windows (excluding WSL2) machines)
59
60
61 --creds=[username[:password]]
62 The [username[:password]] to use to authenticate with the registry, if
63 required. If one or both values are not supplied, a command line
64 prompt appears and the value can be entered. The password is entered
65 without echo.
66
67
68 Note that the specified credentials are only used to authenticate
69 against target registries. They are not used for mirrors or when the
70 registry gets rewritten (see containers-registries.conf(5)); to authen‐
71 ticate against those consider using a containers-auth.json(5) file.
72
73
74 --features
75 Specify the features list which the list or index records as require‐
76 ments for the image. This option is rarely used.
77
78
79 --os
80 Override the OS which the list or index records as a requirement for
81 the image. If imagename refers to a manifest list or image index, the
82 OS information is retrieved from it. Otherwise, it is retrieved from
83 the image's configuration information.
84
85
86 --os-version
87 Specify the OS version which the list or index records as a requirement
88 for the image. This option is rarely used.
89
90
91 --tls-verify
92 Require HTTPS and verify certificates when contacting registries (de‐
93 fault: true). If explicitly set to true, TLS verification is used. If
94 set to false, TLS verification is not used. If not specified, TLS ver‐
95 ification is used unless the target registry is listed as an insecure
96 registry in containers-registries.conf(5)
97
98
99 --variant
100 Specify the variant which the list or index records for the image.
101 This option is typically used to distinguish between multiple entries
102 which share the same architecture value, but which expect different
103 versions of its instruction set.
104
105
107 Multiple transports are supported:
108
109
110 docker://docker-reference (default)
111 An image in a registry implementing the "Docker Registry HTTP API
112 V2". By default, uses the authorization state in $XDG_RUNTIME_DIR/con‐
113 tainers/auth.json, which is set using (podman login). If the authoriza‐
114 tion state is not found there, $HOME/.docker/config.json is checked,
115 which is set using (docker login).
116
117
118 $ podman manifest add mylist:v1.11 docker://quay.io/username/myimage
119
120
121
122 containers-storage:oci-reference
123 An image in oci-reference format stored in the local container stor‐
124 age. oci-reference must contain a tag.
125
126
127 $ podman manifest add mylist:v1.11 containers-storage:quay.io/username/myimage
128
129
130
131 dir:path
132 An existing local directory path storing the manifest, layer tar‐
133 balls, and signatures as individual files. This
134 is a non-standardized format, primarily useful for debugging or non‐
135 invasive container inspection.
136
137
138 $ podman manifest add dir:/tmp/myimage
139
140
141
142 docker-archive:path[:docker-reference]
143 An image is stored in the docker save formatted file. docker-refer‐
144 ence is only used when creating such a
145 file, and it must not contain a digest.
146
147
148 $ podman manifest add docker-archive:/tmp/myimage
149
150
151
152 docker-daemon:docker-reference
153 An image in docker-reference format stored in the docker daemon in‐
154 ternal storage. The docker-reference can also be an image ID (docker-
155 daemon:algo:digest).
156
157
158 $ sudo podman manifest add docker-daemon:docker.io/library/myimage:33
159
160
161
162 oci-archive:path:tag
163 An image tag in a directory compliant with "Open Container Image Lay‐
164 out Specification" at path.
165
166
167 $ podman manifest add oci-archive:/tmp/myimage
168
169
170
172 podman manifest add mylist:v1.11 docker://fedora
173 71c201d10fffdcac52968a000d85a0a016ca1c7d5473948000d3131c1773d965
174
175
176
177 podman manifest add --all mylist:v1.11 docker://fedora
178 71c201d10fffdcac52968a000d85a0a016ca1c7d5473948000d3131c1773d965
179
180
181
182 podman manifest add --arch arm64 --variant v8 mylist:v1.11 docker://71c201d10fffdcac52968a000d85a0a016ca1c7d5473948000d3131c1773d965
183
184
185
187 podman(1), podman-manifest(1)
188
189
190
191 podman-manifest-add(1)