1buildah-push"1"(June 2017) buildah-push"1"(June 2017)
2
6 buildah-push - Push an image from local storage to elsewhere.
7
10 buildah push [options] image [destination]
11
14 Pushes an image from local storage to a specified destination, decom‐
15 pressing and recompessing layers as needed.
16
19 Image stored in local container/storage
20
23 The DESTINATION is a location to store container images. If omitted,
24 the source image parameter will be reused as destination.
25 The Image "DESTINATION" uses a "transport":"details" format. Multiple
28 transports are supported:
29 dir:path
32 An existing local directory path storing the manifest, layer tarballs
33 and signatures as individual files. This is a non-standardized format,
34 primarily useful for debugging or noninvasive container inspection.
35 docker://docker-reference
38 An image in a registry implementing the "Docker Registry HTTP API
39 V2". By default, uses the authorization state in $XDG\_RUN‐
40 TIME\_DIR/containers/auth.json, which is set using (buildah login). If
41 the authorization state is not found there, $HOME/.docker/config.json
42 is checked, which is set using (docker login).
43 If docker-reference does not include a registry name, the image will
44 be pushed to a registry running on localhost.
45 docker-archive:path[:docker-reference]
48 An image is stored in the docker save formatted file. docker-refer‐
49 ence is only used when creating such a file, and it must not contain a
50 digest.
51 docker-daemon:docker-reference
54 An image _dockerreference stored in the docker daemon internal stor‐
55 age. If _dockerreference does not begin with a valid registry name (a
56 domain name containing "." or the reserved name "localhost") then the
57 default registry name "docker.io" will be prepended. _dockerreference
58 must contain either a tag or a digest. Alternatively, when reading
59 images, the format can also be docker-daemon:algo:digest (an image ID).
60 oci:path:tag
63 An image tag in a directory compliant with "Open Container Image Lay‐
64 out Specification" at path.
65 oci-archive:path:tag
68 An image tag in a tar archive compliant with "Open Container Image
69 Layout Specification" at path.
70 ostree:image[@/absolute/repo/path]
73 An image in local OSTree repository. /absolute/repo/path defaults to
74 /ostree/repo.
75 If the transport part of DESTINATION is omitted, "docker://" is
78 assumed.
79
82 --authfile path
83 Path of the authentication file. Default is ${XDG_RUNTIME_DIR}/contain‐
86 ers/auth.json, which is set using buildah login. If the authorization
87 state is not found there, $HOME/.docker/config.json is checked, which
88 is set using docker login.
89 --cert-dir path
92 Use certificates at path (*.crt, *.cert, *.key) to connect to the reg‐
95 istry. Default certificates directory is /etc/containers/certs.d.
96 --creds creds
99 The [username[:password]] to use to authenticate with the registry if
102 required. If one or both values are not supplied, a command line
103 prompt will appear and the value can be entered. The password is
104 entered without echo.
105 --disable-compression, -D
108 Don't compress copies of filesystem layers which will be pushed.
111 --format, -f
114 Manifest Type (oci, v2s1, or v2s2) to use when saving image to direc‐
117 tory using the 'dir:' transport (default is manifest type of source)
118 --quiet, -q
121 When writing the output image, suppress progress output.
124 --tls-verify bool-value
127 Require HTTPS and verify certificates when talking to container reg‐
130 istries (defaults to true)
131
134 This example extracts the imageID image to a local directory in docker
135 format.
136 # buildah push imageID dir:/path/to/image
139 This example extracts the imageID image to a local directory in oci
142 format.
143 # buildah push imageID oci:/path/to/layout:image:tag
146 This example extracts the imageID image to a tar archive in oci format.
149 # buildah push imageID oci-archive:/path/to/archive:image:tag
152 This example extracts the imageID image to a container registry named
155 registry.example.com.
156 # buildah push imageID docker://registry.example.com/repository:tag
159 This example works like docker push, assuming registry.exam‐
162 ple.com/my_image is a local image.
163 # buildah push registry.example.com/my_image
166 This example extracts the imageID image to a private container registry
169 named registry.example.com with authentication from
170 /tmp/auths/myauths.json.
171 # buildah push --authfile /tmp/auths/myauths.json imageID docker://reg‐
174 istry.example.com/repository:tag
175 This example extracts the imageID image and puts into the local docker
178 container store.
179 # buildah push imageID docker-daemon:image:tag
182 This example extracts the imageID image and puts it into the registry
185 on the localhost while turning off tls verification.
186 # buildah push --tls-verify=false imageID docker://local‐
187 host:5000/my-imageID
188 This example extracts the imageID image and puts it into the registry
191 on the localhost using credentials and certificates for authentication.
192 # buildah push --cert-dir /auth --tls-verify=true --creds=user‐
193 name:password imageID docker://localhost:5000/my-imageID
194
197 registries.conf (/etc/containers/registries.conf)
198 registries.conf is the configuration file which specifies which con‐
201 tainer registries should be consulted when completing image names which
202 do not include a registry or domain portion.
203 policy.json (/etc/containers/policy.json)
206 Signature policy file. This defines the trust policy for container
209 images. Controls which container registries can be used for image, and
210 whether or not the tool should trust the images.
211
214 buildah(1), buildah-login(1), policy.json(5), docker-login(1), reg‐
215 istries.conf(5)
216 buildah buildah-push"1"(June 2017)