buildah-push man page

buildah push — Push an image from local storage to elsewhere.

Synopsis

buildah push [options [...]] imageID [destination]

Description

Pushes an image from local storage to a specified destination, decompressing and recompessing layers as needed.

imageID

Image stored in local container/storage

Destination

The DESTINATION is a location to store container images
The Image "DESTINATION" uses a "transport":"details" format.

Multiple transports are supported:

dir:path
 An existing local directory path storing the manifest, layer tarballs and signatures as individual files. This is a non-standardized format, primarily useful for debugging or noninvasive container inspection.

docker://docker-reference
 An image in a registry implementing the "Docker Registry HTTP API V2". By default, uses the authorization state in $HOME/.docker/config.json, which is set e.g. using (docker login).

docker-archive:path[:docker-reference]
 An image is stored in the docker save formatted file.  docker-reference is only used when creating such a file, and it must not contain a digest.

docker-daemon:docker-reference
 An image docker-reference stored in the docker daemon internal storage.  docker-reference must contain either a tag or a digest.  Alternatively, when reading images, the format can also be docker-daemon:algo:digest (an image ID).

oci:path:tag
 An image tag in a directory compliant with "Open Container Image Layout Specification" at path.

ostree:image[@/absolute/repo/path]
 An image in local OSTree repository.  /absolute/repo/path defaults to /ostree/repo.

Options

--cert-dir path
Use certificates at path (*.crt, *.cert, *.key) to connect to the registry
--creds creds
The username[:password] to use to authenticate with the registry if required.
--disable-compression, -D
Don't compress copies of filesystem layers which will be pushed.
--signature-policy
Pathname of a signature policy file to use.  It is not recommended that this option be used, as the default behavior of using the system-wide default policy (frequently /etc/containers/policy.json) is most often preferred.
--tls-verify bool-value
Require HTTPS and verify certificates when talking to container registries (defaults to true)
--quiet
When writing the output image, suppress progress output.

Example

This example extracts the imageID image to a local directory in docker format.

# buildah push imageID dir:/path/to/image

This example extracts the imageID image to a local directory in oci format.

# buildah push imageID oci:/path/to/layout

This example extracts the imageID image to a container registry named registry.example.com.

# buildah push imageID docker://registry.example.com/repository:tag

This example extracts the imageID image and puts into the local docker container store.

# buildah push imageID docker-daemon:image:tag

This example extracts the imageID image and puts it into the registry on the localhost while turning off tls verification.
# buildah push --tls-verify=false imageID docker://localhost:5000/my-imageID

This example extracts the imageID image and puts it into the registry on the localhost using credentials and certificates for authentication.
# buildah push --cert-dir  /auth --tls-verify=true --creds=username:password imageID docker://localhost:5000/my-imageID

See Also

buildah(1)

Info

buildah