.nh
.TH buildah\-commit "1" "March 2017" "buildah"
.SH NAME
.PP
buildah\-commit \- Create an image from a working container.

.SH SYNOPSIS
.PP
\fBbuildah commit\fP [\fIoptions\fP] \fIcontainer\fP [\fIimage\fP]

.SH DESCRIPTION
.PP
Writes a new image using the specified container's read\-write layer and if it
is based on an image, the layers of that image.  If \fIimage\fP does not begin
with a registry name component, \fB\fClocalhost\fR will be added to the name.  If
\fIimage\fP is not provided, the image will have no name.  When an image has no
name, the \fB\fCbuildah images\fR command will display \fB\fC<none>\fR in the \fB\fCREPOSITORY\fR and
\fB\fCTAG\fR columns.

.SH RETURN VALUE
.PP
The image ID of the image that was created.  On error, 1 is returned and errno is returned.

.SH OPTIONS
.PP
\fB\-\-authfile\fP \fIpath\fP

.PP
Path of the authentication file. Default is ${XDG\_RUNTIME\_DIR}/containers/auth.json, which is set using \fB\fCbuildah login\fR\&.
If the authorization state is not found there, $HOME/.docker/config.json is checked, which is set using \fB\fCdocker login\fR\&.

.PP
\fB\-\-cert\-dir\fP \fIpath\fP

.PP
Use certificates at \fIpath\fP (*\&.crt, *\&.cert, *\&.key) to connect to the registry.
The default certificates directory is \fI/etc/containers/certs.d\fP\&.

.PP
\fB\-\-creds\fP \fIcreds\fP

.PP
The [username[:password]] to use to authenticate with the registry if required.
If one or both values are not supplied, a command line prompt will appear and the
value can be entered.  The password is entered without echo.

.PP
\fB\-\-disable\-compression\fP, \fB\-D\fP

.PP
Don't compress filesystem layers when building the image unless it is required
by the location where the image is being written.  This is the default setting,
because image layers are compressed automatically when they are pushed to
registries, and images being written to local storage would only need to be
decompressed again to be stored.  Compression can be forced in all cases by
specifying \fB\-\-disable\-compression=false\fP\&.

.PP
\fB\-\-encryption\-key\fP \fIkey\fP

.PP
The [protocol:keyfile] specifies the encryption protocol, which can be JWE (RFC7516), PGP (RFC4880), and PKCS7 (RFC2315) and the key material required for image encryption. For instance, jwe:/path/to/key.pem or pgp:admin@example.com or pkcs7:/path/to/x509\-file.

.PP
\fB\-\-encrypt\-layer\fP \fIlayer(s)\fP

.PP
Layer(s) to encrypt: 0\-indexed layer indices with support for negative indexing (e.g. 0 is the first layer, \-1 is the last layer). If not defined, will encrypt all layers if encryption\-key flag is specified.

.PP
\fB\-\-format\fP, \fB\-f\fP \fI[oci | docker]\fP

.PP
Control the format for the image manifest and configuration data.  Recognized
formats include \fIoci\fP (OCI image\-spec v1.0, the default) and \fIdocker\fP (version
2, using schema format 2 for the manifest).

.PP
Note: You can also override the default format by setting the BUILDAH\_FORMAT
environment variable.  \fB\fCexport BUILDAH\\\_FORMAT=docker\fR

.PP
\fB\-\-iidfile\fP \fIImageIDfile\fP

.PP
Write the image ID to the file.

.PP
\fB\-\-manifest\fP "manifest"

.PP
Name of the manifest list to which the image will be added. Creates the manifest list
if it does not exist. This option is useful for building multi architecture images.

.PP
\fB\-\-quiet\fP, \fB\-q\fP

.PP
When writing the output image, suppress progress output.

.PP
\fB\-\-rm\fP
Remove the working container and its contents after creating the image.
Default leaves the container and its content in place.

.PP
\fB\-\-sign\-by\fP \fIfingerprint\fP

.PP
Sign the new image using the GPG key that matches the specified fingerprint.

.PP
\fB\-\-squash\fP

.PP
Squash all of the new image's layers (including those inherited from a base image) into a single new layer.

.PP
\fB\-\-timestamp\fP \fIseconds\fP

.PP
Set the create timestamp to seconds since epoch to allow for deterministic builds (defaults to current time).
By default, the created timestamp is changed and written into the image manifest with every commit,
causing the image's sha256 hash to be different even if the sources are exactly the same otherwise.
When \-\-timestamp is set, the created timestamp is always set to the time specified and therefore not changed, allowing the image's sha256 to remain the same. All files committed to the layers of the image will be created with the timestamp.

.PP
\fB\-\-tls\-verify\fP \fIbool\-value\fP

.PP
Require HTTPS and verification of certificates when talking to container registries (defaults to true).  TLS verification cannot be used when talking to an insecure registry.

.SH EXAMPLE
.PP
This example saves an image based on the container.
 \fB\fCbuildah commit containerID newImageName\fR

.PP
This example saves an image named newImageName based on the container.
 \fB\fCbuildah commit \-\-rm containerID newImageName\fR

.PP
This example saves an image with no name, removes the working container, and creates a new container using the image's ID.
 \fB\fCbuildah from $(buildah commit \-\-rm containerID)\fR

.PP
This example saves an image based on the container disabling compression.
 \fB\fCbuildah commit \-\-disable\-compression containerID\fR

.PP
This example saves an image named newImageName based on the container disabling compression.
 \fB\fCbuildah commit \-\-disable\-compression containerID newImageName\fR

.PP
This example commits the container to the image on the local registry while turning off tls verification.
 \fB\fCbuildah commit \-\-tls\-verify=false containerID docker://localhost:5000/imageId\fR

.PP
This example commits the container to the image on the local registry using credentials and certificates for authentication.
 \fB\fCbuildah commit \-\-cert\-dir \~/auth  \-\-tls\-verify=true \-\-creds=username:password containerID docker://localhost:5000/imageId\fR

.PP
This example commits the container to the image on the local registry using credentials from the /tmp/auths/myauths.json file and certificates for authentication.
 \fB\fCbuildah commit \-\-authfile /tmp/auths/myauths.json \-\-cert\-dir \~/auth  \-\-tls\-verify=true \-\-creds=username:password containerID docker://localhost:5000/imageName\fR

.PP
This example saves an image based on the container, but stores dates based on epoch time.
\fB\fCbuildah commit \-\-timestamp=0 containerID newImageName\fR

.SS Building an multi\-architecture image using a \-\-manifest option (Requires emulation software)
.PP
.RS

.nf
#!/bin/sh
build() {
	ctr=$(./bin/buildah from \-\-arch $1 ubi8)
	./bin/buildah run $ctr dnf install \-y iputils
	./bin/buildah commit \-\-manifest ubi8ping $ctr
}
build arm
build amd64
build s390x

.fi
.RE

.SH ENVIRONMENT
.PP
\fBBUILD\_REGISTRY\_SOURCES\fP

.PP
BUILD\_REGISTRY\_SOURCES, if set, is treated as a JSON object which contains
lists of registry names under the keys \fB\fCinsecureRegistries\fR,
\fB\fCblockedRegistries\fR, and \fB\fCallowedRegistries\fR\&.

.PP
When committing an image, if the image is to be given a name, the portion of
the name that corresponds to a registry is compared to the items in the
\fB\fCblockedRegistries\fR list, and if it matches any of them, the commit attempt is
denied.  If there are registries in the \fB\fCallowedRegistries\fR list, and the
portion of the name that corresponds to the registry is not in the list, the
commit attempt is denied.

.PP
\fBTMPDIR\fP
The TMPDIR environment variable allows the user to specify where temporary files
are stored while pulling and pushing images.  Defaults to '/var/tmp'.

.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.

.PP
\fBpolicy.json\fP (\fB\fC/etc/containers/policy.json\fR)

.PP
Signature policy file.  This defines the trust policy for container images.  Controls which container registries can be used for image, and whether or not the tool should trust the images.

.SH SEE ALSO
.PP
buildah(1), buildah\-images(1), containers\-policy.json(5), containers\-registries.conf(5)