Bump to containers/buildah 1.9.2

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>

1 files changed, 15 insertions, 0 deletions

diff --git a/docs/source/markdown/podman-build.1.md b/docs/source/markdown/podman-build.1.md
index 32b14a267..29f763d54 100644
--- a/docs/source/markdown/podman-build.1.md
+++ b/docs/source/markdown/podman-build.1.md
@@ -388,6 +388,11 @@ Adjust the logging level up or down.  Valid option values range from -2 to 3,
 with 3 being roughly equivalent to using the global *--debug* option, and
 values below 0 omitting even error messages which accompany fatal errors.
 
+#### **--manifest** "manifest"
+
+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.
+
 #### **--memory**, **-m**=*LIMIT*
 Memory limit (format: <number>[<unit>], where unit = b (bytes), k (kilobytes),
 m (megabytes), or g (gigabytes))
@@ -667,6 +672,10 @@ that the UTS namespace in which `podman` itself is being run should be reused,
 or it can be the path to a UTS namespace which is already in use by another
 process.
 
+#### **--variant**=""
+
+Set the architecture variant of the image to be pulled.
+
 #### **--volume**, **-v**[=*[HOST-DIR:CONTAINER-DIR[:OPTIONS]]*]
 
    Create a bind mount. If you specify, ` -v /HOST-DIR:/CONTAINER-DIR`, Podman
@@ -811,6 +820,12 @@ $ podman build --layers --force-rm -t imageName .
 $ podman build --no-cache --rm=false -t imageName .
 ```
 
+### Building an multi-architecture image using a --manifest option (Requires emulation software)
+
+podman build --arch arm --manifest myimage /tmp/mysrc
+podman build --arch amd64 --manifest myimage /tmp/mysrc
+podman build --arch s390x --manifest myimage /tmp/mysrc
+
 ### Building an image using a URL, Git repo, or archive
 
   The build context directory can be specified as a URL to a Containerfile, a