41 changed files with 2364 additions and 1519 deletions
--- a/.gitignore
+++ b/.gitignore
@ -0,0 +1 @@
 /*.tar.gz
--- a/SOURCES/001-rhel-shortnames-pyxis.conf
+++ b/SOURCES/001-rhel-shortnames-pyxis.conf
--- a/SOURCES/002-rhel-shortnames-overrides.conf
+++ b/SOURCES/002-rhel-shortnames-overrides.conf
--- a/SOURCES/Containerfile.5.md
+++ b/SOURCES/Containerfile.5.md
@ -9,7 +9,7 @@ Containerfile(Dockerfile) - automate the steps of creating a container image
 The **Containerfile** is a configuration file that automates the steps of creating a container image. It is similar to a Makefile. Container engines (Podman, Buildah, Docker) read instructions from the **Containerfile** to automate the steps otherwise performed manually to create an image. To build an image, create a file called **Containerfile**.
 The **Containerfile** describes the steps taken to assemble the image. When the
-**Containerfile** has been created, call the `buildah bud`, `podman build`, `docker build` command,
+**Containerfile** has been created, call the `buildah build`, `podman build`, `docker build` command,
 using the path of context directory that contains **Containerfile** as the argument. Podman and Buildah default to **Containerfile** and will fall back to **Dockerfile**. Docker only will search for **Dockerfile** in the context directory.
@ -31,7 +31,7 @@ A Containerfile is similar to a Makefile.
 # USAGE
  ```
-  buildah bud .
+  buildah build .
  podman build .
  ```
@ -40,7 +40,7 @@ A Containerfile is similar to a Makefile.
  build.
  ```
-  buildah bud -t repository/tag .
+  buildah build -t repository/tag .
  podman build -t repository/tag .
  ```
@ -61,7 +61,7 @@ A Containerfile is similar to a Makefile.
  `FROM image@digest [AS <name>]`
  -- The **FROM** instruction sets the base image for subsequent instructions. A
-  valid Containerfile must have either **ARG** or *FROM** as its first instruction.
+  valid Containerfile must have either **ARG** or **FROM** as its first instruction.
  If **FROM** is not the first instruction in the file, it may only be preceded by
  one or more ARG instructions, which declare arguments that are used in the next FROM line in the Containerfile.
  The image can be any valid image. It is easy to start by pulling an image from the public
@ -109,7 +109,7 @@ Current supported mount TYPES are bind, cache, secret and tmpfs.
       e.g.
-       mount=type=bind,source=/path/on/host,destination=/path/in/container
+       mount=type=bind,source=/path/on/host,destination=/path/in/container,relabel=shared
       mount=type=tmpfs,tmpfs-size=512M,destination=/path/in/container
@ -131,6 +131,18 @@ Current supported mount TYPES are bind, cache, secret and tmpfs.
 	      · from: stage or image name for the root of the source. Defaults to the build context.
 	      · relabel=shared, z: Relabels src content with a shared label.
 	      . relabel=private, Z: Relabels src content with a private label.
 	      Labeling systems like SELinux require proper labels on the bind mounted content mounted into a container. Without a label, the security system might prevent the processes running in side the container from using the content. By default, container engines do not change the labels set by the OS. The relabel flag tells the engine to relabel file objects on the shared mountz.
 	      The relabel=shared and z options tell the engine that two or more containers will share the mount content. The engine labels the content with a shared content label.
 	      The relabel=private and Z options tell the engine to label the content with a private unshared label. Only the current container can use a private mount.
 	      Relabeling walks the file system under the mount and changes the label on each file, if the mount has thousands of inodes, this process takes a long time, delaying the start of the container.
 	      · rw, read-write: allows writes on the mount.
       Options specific to tmpfs:
@ -207,7 +219,7 @@ Container engines pass secret the secret file into the build using the `--secret
 **--mount**=*type=secret,TYPE-SPECIFIC-OPTION[,...]*
- `id` is the identifier for the secret passed into the `buildah bud --secret` or `podman build --secret`. This identifier is associated with the RUN --mount identifier to use in the Containerfile.
+- `id` is the identifier for the secret passed into the `buildah build --secret` or `podman build --secret`. This identifier is associated with the RUN --mount identifier to use in the Containerfile.
 - `dst`|`target`|`destination` rename the secret file to a specific file in the Containerfile RUN command to use.
@ -224,7 +236,7 @@ RUN --mount=type=secret,id=mysecret,dst=/foobar cat /foobar
 The secret needs to be passed to the build using the --secret flag. The final image built does not container the secret file:
 ```
- buildah bud --no-cache --secret id=mysecret,src=mysecret.txt .
+ buildah build --no-cache --secret id=mysecret,src=mysecret.txt .
 ```
  -- The **RUN** instruction executes any commands in a new layer on top of the current
@ -463,7 +475,7 @@ The secret needs to be passed to the build using the --secret flag. The final im
  In the above example, the output of the **pwd** command is **a/b/c**.
 **ARG**
-   -- ARG <name>[=<default value>]
+   -- `ARG <name>[=<default value>]`
  The `ARG` instruction defines a variable that users can pass at build-time to
  the builder with the `podman build` and `buildah build` commands using the
@ -594,6 +606,56 @@ The secret needs to be passed to the build using the --secret flag. The final im
  $ podman build --build-arg HTTPS_PROXY=https://my-proxy.example.com .
  ```
 **Platform/OS/Arch ARG**
   -- `ARG <name>`
  When building multi-arch manifest-lists or images for a foreign-architecture,
  it's often helpful to have access to platform details within the `Containerfile`.
  For example, when using a `RUN curl ...` command to install OS/Arch specific
  binary into the image.  Or, if certain `RUN` operations are known incompatible
  or non-performant when emulating a specific architecture.
  There are several named `ARG` variables available. The purpose of each should be
  self-evident by its name.  _However_, in all cases these ARG values are **not**
  automatically populated.  You must always declare them within each `FROM` section
  of the `Containerfile`.
  The available `ARG <name>` variables are available with two prefixes:
  * `TARGET...` variable names represent details about the currently running build
    context (i.e. "inside" the container).  These are often the most useful:
    * `TARGETOS`: For example `linux`
    * `TARGETARCH`: For example `amd64`
    * `TARGETPLATFORM`: For example `linux/amd64`
    * `TARGETVARIANT`: Uncommonly used, specific to `TARGETARCH`
  * `BUILD...` variable names signify details about the _host_ performing the build
    (i.e. "outside" the container):
    * `BUILDOS`: OS of host performing the build
    * `BUILDARCH`: Arch of host performing the build
    * `BUILDPLATFORM`: Combined OS/Arch of host performing the build
    * `BUILDVARIANT`: Uncommonly used, specific to `BUILDARCH`
  An example `Containerfile` that uses `TARGETARCH` to fetch an arch-specific binary could be:
  ```
  FROM busybox
  ARG TARGETARCH
  RUN curl -sSf -O https://example.com/downloads/bin-${TARGETARCH}.zip
  ```
  Assuming the host platform is `linux/amd64` and foreign-architecture emulation
  enabled (e.g. `qemu-user-static`), then running the command:
  ```
  $ podman build --platform linux/s390x .
  ```
  Would end up running `curl` on `https://example.com/downloads/bin-s390x.zip` and producing
  a container image suited for the the `linux/s390x` platform.  **Note:** Emulation isn't
  strictly required, these special build-args will also function when building using
  `podman farm build`.
 **ONBUILD**
  -- `ONBUILD [INSTRUCTION]`
  The **ONBUILD** instruction adds a trigger instruction to an image. The
--- a/5
+++ b/5
@ -0,0 +1,5 @@
 -----BEGIN PUBLIC KEY-----
 MHYwEAYHKoZIzj0CAQYFK4EEACIDYgAENqXXmPchbztil/PU0uGBh4xYJkterHN0
 Yz/o/cXw2hmmr6WAjq0FIEilS5nlDM9La+RcBts4xekrPBKBn37thbYuCoxEH39U
 gmagLaBS92UAhZty93CXgXMy89h5pJFZ
 -----END PUBLIC KEY-----
--- a/22
+++ b/22
@ -0,0 +1,22 @@
 The following key is used to provide verification of sigstore signatures for
 artifacts that are sigstore-enabled.
 Questions about this key should be sent to security@redhat.com
 pub   4096R/E60D446E63405576 2024-09-20
 uid                          Red Hat, Inc. (release key 3) <security@redhat.com>
 -----BEGIN PUBLIC KEY-----
 MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA0ASyuH2TLWvBUqPHZ4Ip
 75g7EncBkgQHdJnjzxAW5KQTMh/siBoB/BoSrtiPMwnChbTCnQOIQeZuDiFnhuJ7
 M/D3b7JoX0m123NcCSn67mAdjBa6Bg6kukZgCP4ZUZeESajWX/EjylFcRFOXW57p
 RDCEN42J/jYlVqt+g9+Grker8Sz86H3l0tbqOdjbz/VxHYhwF0ctUMHsyVRDq2QP
 tqzNXlmlMhS/PoFr6R4u/7HCn/K+LegcO2fAFOb40KvKSKKVD6lewUZErhop1CgJ
 XjDtGmmO9dGMF71mf6HEfaKSdy+EE6iSF2A2Vv9QhBawMiq2kOzEiLg4nAdJT8wg
 ZrMAmPCqGIsXNGZ4/Q+YTwwlce3glqb5L9tfNozEdSR9N85DESfQLQEdY3CalwKM
 BT1OEhEX1wHRCU4drMOej6BNW0VtscGtHmCrs74jPezhwNT8ypkyS+T0zT4Tsy6f
 VXkJ8YSHyenSzMB2Op2bvsE3grY+s74WhG9UIA6DBxcTie15NSzKwfzaoNWODcLF
 p7BY8aaHE2MqFxYFX+IbjpkQRfaeQQsouDFdCkXEFVfPpbD2dk6FleaMTPuyxtIT
 gjVEtGQK2qGCFGiQHFd4hfV+eCA63Jro1z0zoBM5BbIIQ3+eVFwt3AlZp5UVwr6d
 secqki/yrmv3Y0dqZ9VOn3UCAwEAAQ==
 -----END PUBLIC KEY-----
--- a/SOURCES/RPM-GPG-KEY-redhat-beta
+++ b/SOURCES/RPM-GPG-KEY-redhat-beta
@ -1,29 +0,0 @@
 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.6 (GNU/Linux)
 mQINBEmkAzABEAC2/c7bP1lHQ3XScxbIk0LQWe1YOiibQBRLwf8Si5PktgtuPibT
 kKpZjw8p4D+fM7jD1WUzUE0X7tXg2l/eUlMM4dw6XJAQ1AmEOtlwSg7rrMtTvM0A
 BEtI7Km6fC6sU6RtBMdcqD1cH/6dbsfh8muznVA7UlX+PRBHVzdWzj6y8h84dBjo
 gzcbYu9Hezqgj/lLzicqsSZPz9UdXiRTRAIhp8V30BD8uRaaa0KDDnD6IzJv3D9P
 xQWbFM4Z12GN9LyeZqmD7bpKzZmXG/3drvfXVisXaXp3M07t3NlBa3Dt8NFIKZ0D
 FRXBz5bvzxRVmdH6DtkDWXDPOt+Wdm1rZrCOrySFpBZQRpHw12eo1M1lirANIov7
 Z+V1Qh/aBxj5EUu32u9ZpjAPPNtQF6F/KjaoHHHmEQAuj4DLex4LY646Hv1rcv2i
 QFuCdvLKQGSiFBrfZH0j/IX3/0JXQlZzb3MuMFPxLXGAoAV9UP/Sw/WTmAuTzFVm
 G13UYFeMwrToOiqcX2VcK0aC1FCcTP2z4JW3PsWvU8rUDRUYfoXovc7eg4Vn5wHt
 0NBYsNhYiAAf320AUIHzQZYi38JgVwuJfFu43tJZE4Vig++RQq6tsEx9Ftz3EwRR
 fJ9z9mEvEiieZm+vbOvMvIuimFVPSCmLH+bI649K8eZlVRWsx3EXCVb0nQARAQAB
 tDBSZWQgSGF0LCBJbmMuIChiZXRhIGtleSAyKSA8c2VjdXJpdHlAcmVkaGF0LmNv
 bT6JAjYEEwECACAFAkpSM+cCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRCT
 ioDK8hVB6/9tEAC0+KmzeKceXQ/GTUoU6jy9vtkFCFrmv+c7ol4XpdTt0QhqBOwy
 6m2mKWwmm8KfYfy0cADQ4y/EcoXl7FtFBwYmkCuEQGXhTDn9DvVjhooIq59LEMBQ
 OW879RwwzRIZ8ebbjMUjDPF5MfPQqP2LBu9N4KvXlZp4voykwuuaJ+cbsKZR6pZ6
 0RQKPHKP+NgUFC0fff7XY9cuOZZWFAeKRhLN2K7bnRHKxp+kELWb6R9ZfrYwZjWc
 MIPbTd1khE53L4NTfpWfAnJRtkPSDOKEGVlVLtLq4HEAxQt07kbslqISRWyXER3u
 QOJj64D1ZiIMz6t6uZ424VE4ry9rBR0Jz55cMMx5O/ni9x3xzFUgH8Su2yM0r3jE
 Rf24+tbOaPf7tebyx4OKe+JW95hNVstWUDyGbs6K9qGfI/pICuO1nMMFTo6GqzQ6
 DwLZvJ9QdXo7ujEtySZnfu42aycaQ9ZLC2DOCQCUBY350Hx6FLW3O546TAvpTfk0
 B6x+DV7mJQH7MGmRXQsE7TLBJKjq28Cn4tVp04PmybQyTxZdGA/8zY6pPl6xyVMH
 V68hSBKEVT/rlouOHuxfdmZva1DhVvUC6Xj7+iTMTVJUAq/4Uyn31P1OJmA2a0PT
 CAqWkbJSgKFccsjPoTbLyxhuMSNkEZFHvlZrSK9vnPzmfiRH0Orx3wYpMQ==
 =21pb
 -----END PGP PUBLIC KEY BLOCK-----
--- a/SOURCES/RPM-GPG-KEY-redhat-release
+++ b/SOURCES/RPM-GPG-KEY-redhat-release
@ -1,66 +0,0 @@
 The following public key can be used to verify RPM packages built and
 signed by Red Hat, Inc.  This key is used for packages in Red Hat
 products shipped after November 2009, and for all updates to those
 products.
 Questions about this key should be sent to security@redhat.com.
 pub  4096R/FD431D51 2009-10-22 Red Hat, Inc. (release key 2) <security@redhat.com>
 -----BEGIN PGP PUBLIC KEY BLOCK-----
 mQINBErgSTsBEACh2A4b0O9t+vzC9VrVtL1AKvUWi9OPCjkvR7Xd8DtJxeeMZ5eF
 0HtzIG58qDRybwUe89FZprB1ffuUKzdE+HcL3FbNWSSOXVjZIersdXyH3NvnLLLF
 0DNRB2ix3bXG9Rh/RXpFsNxDp2CEMdUvbYCzE79K1EnUTVh1L0Of023FtPSZXX0c
 u7Pb5DI5lX5YeoXO6RoodrIGYJsVBQWnrWw4xNTconUfNPk0EGZtEnzvH2zyPoJh
 XGF+Ncu9XwbalnYde10OCvSWAZ5zTCpoLMTvQjWpbCdWXJzCm6G+/hx9upke546H
 5IjtYm4dTIVTnc3wvDiODgBKRzOl9rEOCIgOuGtDxRxcQkjrC+xvg5Vkqn7vBUyW
 9pHedOU+PoF3DGOM+dqv+eNKBvh9YF9ugFAQBkcG7viZgvGEMGGUpzNgN7XnS1gj
 /DPo9mZESOYnKceve2tIC87p2hqjrxOHuI7fkZYeNIcAoa83rBltFXaBDYhWAKS1
 PcXS1/7JzP0ky7d0L6Xbu/If5kqWQpKwUInXtySRkuraVfuK3Bpa+X1XecWi24JY
 HVtlNX025xx1ewVzGNCTlWn1skQN2OOoQTV4C8/qFpTW6DTWYurd4+fE0OJFJZQF
 buhfXYwmRlVOgN5i77NTIJZJQfYFj38c/Iv5vZBPokO6mffrOTv3MHWVgQARAQAB
 tDNSZWQgSGF0LCBJbmMuIChyZWxlYXNlIGtleSAyKSA8c2VjdXJpdHlAcmVkaGF0
 LmNvbT6JAjYEEwECACAFAkrgSTsCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAK
 CRAZni+R/UMdUWzpD/9s5SFR/ZF3yjY5VLUFLMXIKUztNN3oc45fyLdTI3+UClKC
 2tEruzYjqNHhqAEXa2sN1fMrsuKec61Ll2NfvJjkLKDvgVIh7kM7aslNYVOP6BTf
 C/JJ7/ufz3UZmyViH/WDl+AYdgk3JqCIO5w5ryrC9IyBzYv2m0HqYbWfphY3uHw5
 un3ndLJcu8+BGP5F+ONQEGl+DRH58Il9Jp3HwbRa7dvkPgEhfFR+1hI+Btta2C7E
 0/2NKzCxZw7Lx3PBRcU92YKyaEihfy/aQKZCAuyfKiMvsmzs+4poIX7I9NQCJpyE
 IGfINoZ7VxqHwRn/d5mw2MZTJjbzSf+Um9YJyA0iEEyD6qjriWQRbuxpQXmlAJbh
 8okZ4gbVFv1F8MzK+4R8VvWJ0XxgtikSo72fHjwha7MAjqFnOq6eo6fEC/75g3NL
 Ght5VdpGuHk0vbdENHMC8wS99e5qXGNDued3hlTavDMlEAHl34q2H9nakTGRF5Ki
 JUfNh3DVRGhg8cMIti21njiRh7gyFI2OccATY7bBSr79JhuNwelHuxLrCFpY7V25
 OFktl15jZJaMxuQBqYdBgSay2G0U6D1+7VsWufpzd/Abx1/c3oi9ZaJvW22kAggq
 dzdA27UUYjWvx42w9menJwh/0jeQcTecIUd0d0rFcw/c1pvgMMl/Q73yzKgKYw==
 =zbHE
 -----END PGP PUBLIC KEY BLOCK-----
 -----BEGIN PGP PUBLIC KEY BLOCK-----
 mQINBGIpIp4BEAC/o5e1WzLIsS6/JOQCs4XYATYTcf6B6ALzcP05G0W3uRpUQSrL
 FRKNrU8ZCelm/B+XSh2ljJNeklp2WLxYENDOsftDXGoyLr2hEkI5OyK267IHhFNJ
 g+BN+T5Cjh4ZiiWij6o9F7x2ZpxISE9M4iI80rwSv1KOnGSw5j2zD2EwoMjTVyVE
 /t3s5XJxnDclB7ZqL+cgjv0mWUY/4+b/OoRTkhq7b8QILuZp75Y64pkrndgakm1T
 8mAGXV02mEzpNj9DyAJdUqa11PIhMJMxxHOGHJ8CcHZ2NJL2e7yJf4orTj+cMhP5
 LzJcVlaXnQYu8Zkqa0V6J1Qdj8ZXL72QsmyicRYXAtK9Jm5pvBHuYU2m6Ja7dBEB
 Vkhe7lTKhAjkZC5ErPmANNS9kPdtXCOpwN1lOnmD2m04hks3kpH9OTX7RkTFUSws
 eARAfRID6RLfi59B9lmAbekecnsMIFMx7qR7ZKyQb3GOuZwNYOaYFevuxusSwCHv
 4FtLDIhk+Fge+EbPdEva+VLJeMOb02gC4V/cX/oFoPkxM1A5LHjkuAM+aFLAiIRd
 Np/tAPWk1k6yc+FqkcDqOttbP4ciiXb9JPtmzTCbJD8lgH0rGp8ufyMXC9x7/dqX
 TjsiGzyvlMnrkKB4GL4DqRFl8LAR02A3846DD8CAcaxoXggL2bJCU2rgUQARAQAB
 tDVSZWQgSGF0LCBJbmMuIChhdXhpbGlhcnkga2V5IDMpIDxzZWN1cml0eUByZWRo
 YXQuY29tPokCUgQTAQgAPBYhBH5GJCWMQGU11W1vE1BU5KRaY0CzBQJiKSKeAhsD
 BQsJCAcCAyICAQYVCgkICwIEFgIDAQIeBwIXgAAKCRBQVOSkWmNAsyBfEACuTN/X
 YR+QyzeRw0pXcTvMqzNE4DKKr97hSQEwZH1/v1PEPs5O3psuVUm2iam7bqYwG+ry
 EskAgMHi8AJmY0lioQD5/LTSLTrM8UyQnU3g17DHau1NHIFTGyaW4a7xviU4C2+k
 c6X0u1CPHI1U4Q8prpNcfLsldaNYlsVZtUtYSHKPAUcswXWliW7QYjZ5tMSbu8jR
 OMOc3mZuf0fcVFNu8+XSpN7qLhRNcPv+FCNmk/wkaQfH4Pv+jVsOgHqkV3aLqJeN
 kNUnpyEKYkNqo7mNfNVWOcl+Z1KKKwSkIi3vg8maC7rODsy6IX+Y96M93sqYDQom
 aaWue2gvw6thEoH4SaCrCL78mj2YFpeg1Oew4QwVcBnt68KOPfL9YyoOicNs4Vuu
 fb/vjU2ONPZAeepIKA8QxCETiryCcP43daqThvIgdbUIiWne3gae6eSj0EuUPoYe
 H5g2Lw0qdwbHIOxqp2kvN96Ii7s1DK3VyhMt/GSPCxRnDRJ8oQKJ2W/I1IT5VtiU
 zMjjq5JcYzRPzHDxfVzT9CLeU/0XQ+2OOUAiZKZ0dzSyyVn8xbpviT7iadvjlQX3
 CINaPB+d2Kxa6uFWh+ZYOLLAgZ9B8NKutUHpXN66YSfe79xFBSFWKkJ8cSIMk13/
 Ifs7ApKlKCCRDpwoDqx/sjIaj1cpOfLHYjnefg==
 =UZd/
 -----END PGP PUBLIC KEY BLOCK-----
--- a/SOURCES/registry.access.redhat.com.yaml
+++ b/SOURCES/registry.access.redhat.com.yaml
@ -1,3 +0,0 @@
 docker:
     registry.access.redhat.com:
         sigstore: https://access.redhat.com/webassets/docker/content/sigstore
--- a/SOURCES/registry.redhat.io.yaml
+++ b/SOURCES/registry.redhat.io.yaml
@ -1,3 +0,0 @@
 docker:
     registry.redhat.io:
         sigstore: https://registry.redhat.io/containers/sigstore
--- a/SOURCES/storage.conf
+++ b/SOURCES/storage.conf
@ -1,243 +0,0 @@
 # This file is the configuration file for all tools
 # that use the containers/storage library. The storage.conf file
 # overrides all other storage.conf files. Container engines using the
 # container/storage library do not inherit fields from other storage.conf
 # files.
 #
 #  Note: The storage.conf file overrides other storage.conf files based on this precedence:
 #      /usr/containers/storage.conf
 #      /etc/containers/storage.conf
 #      $HOME/.config/containers/storage.conf
 #      $XDG_CONFIG_HOME/containers/storage.conf (If XDG_CONFIG_HOME is set)
 # See man 5 containers-storage.conf for more information
 # The "container storage" table contains all of the server options.
 [storage]
 # Default Storage Driver, Must be set for proper operation.
 driver = "overlay"
 # Temporary storage location
 runroot = "/run/containers/storage"
 # Primary Read/Write location of container storage
 # When changing the graphroot location on an SELINUX system, you must
 # ensure  the labeling matches the default locations labels with the
 # following commands:
 # semanage fcontext -a -e /var/lib/containers/storage /NEWSTORAGEPATH
 # restorecon -R -v /NEWSTORAGEPATH
 graphroot = "/var/lib/containers/storage"
 # Optional alternate location of image store if a location separate from the
 # container store is required. If set, it must be different than graphroot.
 # imagestore = ""
 # Storage path for rootless users
 #
 # rootless_storage_path = "$HOME/.local/share/containers/storage"
 # Transient store mode makes all container metadata be saved in temporary storage
 # (i.e. runroot above). This is faster, but doesn't persist across reboots.
 # Additional garbage collection must also be performed at boot-time, so this
 # option should remain disabled in most configurations.
 # transient_store = true
 [storage.options]
 # Storage options to be passed to underlying storage drivers
 # AdditionalImageStores is used to pass paths to additional Read/Only image stores
 # Must be comma separated list.
 additionalimagestores = [
 ]
 # Allows specification of how storage is populated when pulling images. This
 # option can speed the pulling process of images compressed with format
 # zstd:chunked. Containers/storage looks for files within images that are being
 # pulled from a container registry that were previously pulled to the host.  It
 # can copy or create a hard link to the existing file when it finds them,
 # eliminating the need to pull them from the container registry. These options
 # can deduplicate pulling of content, disk storage of content and can allow the
 # kernel to use less memory when running containers.
 # containers/storage supports three keys
 #   * enable_partial_images="true" | "false"
 #     Tells containers/storage to look for files previously pulled in storage
 #     rather then always pulling them from the container registry.
 #   * use_hard_links = "false" | "true"
 #     Tells containers/storage to use hard links rather then create new files in
 #     the image, if an identical file already existed in storage.
 #   * ostree_repos = ""
 #     Tells containers/storage where an ostree repository exists that might have
 #     previously pulled content which can be used when attempting to avoid
 #     pulling content from the container registry
 pull_options = {enable_partial_images = "false", use_hard_links = "false", ostree_repos=""}
 # Remap-UIDs/GIDs is the mapping from UIDs/GIDs as they should appear inside of
 # a container, to the UIDs/GIDs as they should appear outside of the container,
 # and the length of the range of UIDs/GIDs.  Additional mapped sets can be
 # listed and will be heeded by libraries, but there are limits to the number of
 # mappings which the kernel will allow when you later attempt to run a
 # container.
 #
 # remap-uids = "0:1668442479:65536"
 # remap-gids = "0:1668442479:65536"
 # Remap-User/Group is a user name which can be used to look up one or more UID/GID
 # ranges in the /etc/subuid or /etc/subgid file.  Mappings are set up starting
 # with an in-container ID of 0 and then a host-level ID taken from the lowest
 # range that matches the specified name, and using the length of that range.
 # Additional ranges are then assigned, using the ranges which specify the
 # lowest host-level IDs first, to the lowest not-yet-mapped in-container ID,
 # until all of the entries have been used for maps. This setting overrides the
 # Remap-UIDs/GIDs setting.
 #
 # remap-user = "containers"
 # remap-group = "containers"
 # Root-auto-userns-user is a user name which can be used to look up one or more UID/GID
 # ranges in the /etc/subuid and /etc/subgid file.  These ranges will be partitioned
 # to containers configured to create automatically a user namespace.  Containers
 # configured to automatically create a user namespace can still overlap with containers
 # having an explicit mapping set.
 # This setting is ignored when running as rootless.
 # root-auto-userns-user = "storage"
 #
 # Auto-userns-min-size is the minimum size for a user namespace created automatically.
 # auto-userns-min-size=1024
 #
 # Auto-userns-max-size is the maximum size for a user namespace created automatically.
 # auto-userns-max-size=65536
 [storage.options.overlay]
 # ignore_chown_errors can be set to allow a non privileged user running with
 # a single UID within a user namespace to run containers. The user can pull
 # and use any image even those with multiple uids.  Note multiple UIDs will be
 # squashed down to the default uid in the container.  These images will have no
 # separation between the users in the container. Only supported for the overlay
 # and vfs drivers.
 #ignore_chown_errors = "false"
 # Inodes is used to set a maximum inodes of the container image.
 # inodes = ""
 # Path to an helper program to use for mounting the file system instead of mounting it
 # directly.
 #mount_program = "/usr/bin/fuse-overlayfs"
 # mountopt specifies comma separated list of extra mount options
 mountopt = "nodev,metacopy=on"
 # Set to skip a PRIVATE bind mount on the storage home directory.
 # skip_mount_home = "false"
 # Size is used to set a maximum size of the container image.
 # size = ""
 # ForceMask specifies the permissions mask that is used for new files and
 # directories.
 #
 # The values "shared" and "private" are accepted.
 # Octal permission masks are also accepted.
 #
 #  "": No value specified.
 #     All files/directories, get set with the permissions identified within the
 #     image.
 #  "private": it is equivalent to 0700.
 #     All files/directories get set with 0700 permissions.  The owner has rwx
 #     access to the files. No other users on the system can access the files.
 #     This setting could be used with networked based homedirs.
 #  "shared": it is equivalent to 0755.
 #     The owner has rwx access to the files and everyone else can read, access
 #     and execute them. This setting is useful for sharing containers storage
 #     with other users.  For instance have a storage owned by root but shared
 #     to rootless users as an additional store.
 #     NOTE:  All files within the image are made readable and executable by any
 #     user on the system. Even /etc/shadow within your image is now readable by
 #     any user.
 #
 #   OCTAL: Users can experiment with other OCTAL Permissions.
 #
 #  Note: The force_mask Flag is an experimental feature, it could change in the
 #  future.  When "force_mask" is set the original permission mask is stored in
 #  the "user.containers.override_stat" xattr and the "mount_program" option must
 #  be specified. Mount programs like "/usr/bin/fuse-overlayfs" present the
 #  extended attribute permissions to processes within containers rather than the
 #  "force_mask"  permissions.
 #
 # force_mask = ""
 [storage.options.thinpool]
 # Storage Options for thinpool
 # autoextend_percent determines the amount by which pool needs to be
 # grown. This is specified in terms of % of pool size. So a value of 20 means
 # that when threshold is hit, pool will be grown by 20% of existing
 # pool size.
 # autoextend_percent = "20"
 # autoextend_threshold determines the pool extension threshold in terms
 # of percentage of pool size. For example, if threshold is 60, that means when
 # pool is 60% full, threshold has been hit.
 # autoextend_threshold = "80"
 # basesize specifies the size to use when creating the base device, which
 # limits the size of images and containers.
 # basesize = "10G"
 # blocksize specifies a custom blocksize to use for the thin pool.
 # blocksize="64k"
 # directlvm_device specifies a custom block storage device to use for the
 # thin pool. Required if you setup devicemapper.
 # directlvm_device = ""
 # directlvm_device_force wipes device even if device already has a filesystem.
 # directlvm_device_force = "True"
 # fs specifies the filesystem type to use for the base device.
 # fs="xfs"
 # log_level sets the log level of devicemapper.
 # 0: LogLevelSuppress 0 (Default)
 # 2: LogLevelFatal
 # 3: LogLevelErr
 # 4: LogLevelWarn
 # 5: LogLevelNotice
 # 6: LogLevelInfo
 # 7: LogLevelDebug
 # log_level = "7"
 # min_free_space specifies the min free space percent in a thin pool require for
 # new device creation to succeed. Valid values are from 0% - 99%.
 # Value 0% disables
 # min_free_space = "10%"
 # mkfsarg specifies extra mkfs arguments to be used when creating the base
 # device.
 # mkfsarg = ""
 # metadata_size is used to set the `pvcreate --metadatasize` options when
 # creating thin devices. Default is 128k
 # metadata_size = ""
 # Size is used to set a maximum size of the container image.
 # size = ""
 # use_deferred_removal marks devicemapper block device for deferred removal.
 # If the thinpool is in use when the driver attempts to remove it, the driver
 # tells the kernel to remove it as soon as possible. Note this does not free
 # up the disk space, use deferred deletion to fully remove the thinpool.
 # use_deferred_removal = "True"
 # use_deferred_deletion marks thinpool device for deferred deletion.
 # If the device is busy when the driver attempts to delete it, the driver
 # will attempt to delete device every 30 seconds until successful.
 # If the program using the driver exits, the driver will continue attempting
 # to cleanup the next time the driver is used. Deferred deletion permanently
 # deletes the device and all data stored in device will be lost.
 # use_deferred_deletion = "True"
 # xfs_nospace_max_retries specifies the maximum number of retries XFS should
 # attempt to complete IO when ENOSPC (no space) error is returned by
 # underlying storage device.
 # xfs_nospace_max_retries = "0"
--- a/SPECS/containers-common.spec
+++ b/SPECS/containers-common.spec
@ -1,427 +0,0 @@
 # Bellow definitions are used to deliver config files from a particular branch
 # of c/image, c/common, c/storage vendored in all podman, skopeo, buildah.
 # These vendored components must have the same version. If it is not the case,
 # pick the oldest version on c/image, c/common, c/storage vendored in
 # podman/skopeo/podman.
 %global skopeo_branch main
 %global image_branch v5.29.2
 %global common_branch v0.57.3
 %global storage_branch v1.51.0
 %global shortnames_branch main
 Epoch: 2
 Name: containers-common
 Version: 1
 Release: 81%{?dist}
 Summary: Common configuration and documentation for containers
 License: ASL 2.0
 # arch limitation because of go-md2man (missing on i686)
 # https://fedoraproject.org/wiki/PackagingDrafts/Go#Go_Language_Architectures
 ExclusiveArch: %{go_arches}
 BuildRequires: /usr/bin/go-md2man
 Provides: skopeo-containers = %{epoch}:%{version}-%{release}
 Conflicts: %{name} <= 2:1-22
 Obsoletes: %{name} <= 2:1-22
 Requires: (container-selinux >= 2:2.162.1 if selinux-policy)
 Requires: oci-runtime
 %if 0%{?rhel} >= 9 || 0%{?fedora}
 Requires: crun >= 0.19
 %else
 Requires: runc
 %endif
 Requires: system-release
 Suggests: subscription-manager
 Recommends: fuse-overlayfs
 Recommends: slirp4netns
 Source1: https://raw.githubusercontent.com/containers/storage/%{storage_branch}/storage.conf
 Source2: https://raw.githubusercontent.com/containers/storage/%{storage_branch}/docs/containers-storage.conf.5.md
 Source3: mounts.conf
 Source4: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-registries.conf.5.md
 #Source5: https://raw.githubusercontent.com/containers/image/%%{image_branch}/registries.conf
 Source5: registries.conf
 Source6: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-policy.json.5.md
 Source7: https://raw.githubusercontent.com/containers/common/%{common_branch}/pkg/seccomp/seccomp.json
 Source8: https://raw.githubusercontent.com/containers/common/%{common_branch}/docs/containers-mounts.conf.5.md
 Source9: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-signature.5.md
 Source10: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-transports.5.md
 Source11: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-certs.d.5.md
 Source12: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-registries.d.5.md
 Source13: https://raw.githubusercontent.com/containers/common/%{common_branch}/pkg/config/containers.conf
 Source14: https://raw.githubusercontent.com/containers/common/%{common_branch}/docs/containers.conf.5.md
 Source15: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-auth.json.5.md
 Source16: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-registries.conf.d.5.md
 Source17: https://raw.githubusercontent.com/containers/shortnames/%{shortnames_branch}/shortnames.conf
 Source19: 001-rhel-shortnames-pyxis.conf
 Source20: 002-rhel-shortnames-overrides.conf
 Source21: RPM-GPG-KEY-redhat-release
 Source22: registry.access.redhat.com.yaml
 Source23: registry.redhat.io.yaml
 #Source24: https://raw.githubusercontent.com/containers/skopeo/%%{skopeo_branch}/default-policy.json
 Source24: default-policy.json
 Source25: https://raw.githubusercontent.com/containers/skopeo/%{skopeo_branch}/default.yaml
 # FIXME: fix the branch once these are available via regular c/common branch
 Source26: https://raw.githubusercontent.com/containers/common/main/docs/Containerfile.5.md
 Source27: https://raw.githubusercontent.com/containers/common/main/docs/containerignore.5.md
 Source28: RPM-GPG-KEY-redhat-beta
 # scripts used for synchronization with upstream and shortname generation
 Source100: update.sh
 Source101: update-vendored.sh
 Source102: pyxis.sh
 %description
 This package contains common configuration files and documentation for container
 tools ecosystem, such as Podman, Buildah and Skopeo.
 It is required because the most of configuration files and docs come from projects
 which are vendored into Podman, Buildah, Skopeo, etc. but they are not packaged
 separately.
 %prep
 %build
 %install
 install -dp %{buildroot}%{_sysconfdir}/containers/{certs.d,oci/hooks.d,systemd,registries.d,registries.conf.d}
 install -dp %{buildroot}%{_datadir}/containers/systemd
 install -m0644 %{SOURCE1} %{buildroot}%{_sysconfdir}/containers/storage.conf
 install -m0644 %{SOURCE5} %{buildroot}%{_sysconfdir}/containers/registries.conf
 install -m0644 %{SOURCE17} %{buildroot}%{_sysconfdir}/containers/registries.conf.d/000-shortnames.conf
 install -m0644 %{SOURCE19} %{buildroot}%{_sysconfdir}/containers/registries.conf.d/001-rhel-shortnames.conf
 install -m0644 %{SOURCE20} %{buildroot}%{_sysconfdir}/containers/registries.conf.d/002-rhel-shortnames-overrides.conf
 # for signature verification
 %if !0%{?rhel} || 0%{?centos}
 install -dp %{buildroot}%{_sysconfdir}/pki/rpm-gpg
 install -m0644 %{SOURCE21} %{buildroot}%{_sysconfdir}/pki/rpm-gpg
 install -m0644 %{SOURCE28} %{buildroot}%{_sysconfdir}/pki/rpm-gpg
 %endif
 install -dp %{buildroot}%{_sysconfdir}/containers/registries.d
 install -m0644 %{SOURCE22} %{buildroot}%{_sysconfdir}/containers/registries.d
 install -m0644 %{SOURCE23} %{buildroot}%{_sysconfdir}/containers/registries.d
 install -m0644 %{SOURCE24} %{buildroot}%{_sysconfdir}/containers/policy.json
 install -dp %{buildroot}%{_sharedstatedir}/containers/sigstore
 install -m0644 %{SOURCE25} %{buildroot}%{_sysconfdir}/containers/registries.d/default.yaml
 # for containers-common
 install -dp %{buildroot}%{_mandir}/man5
 go-md2man -in %{SOURCE2} -out %{buildroot}%{_mandir}/man5/containers-storage.conf.5
 go-md2man -in %{SOURCE4} -out %{buildroot}%{_mandir}/man5/containers-registries.conf.5
 go-md2man -in %{SOURCE6} -out %{buildroot}%{_mandir}/man5/containers-policy.json.5
 go-md2man -in %{SOURCE8} -out %{buildroot}%{_mandir}/man5/containers-mounts.conf.5
 go-md2man -in %{SOURCE9} -out %{buildroot}%{_mandir}/man5/containers-signature.5
 go-md2man -in %{SOURCE10} -out %{buildroot}%{_mandir}/man5/containers-transports.5
 go-md2man -in %{SOURCE11} -out %{buildroot}%{_mandir}/man5/containers-certs.d.5
 go-md2man -in %{SOURCE12} -out %{buildroot}%{_mandir}/man5/containers-registries.d.5
 go-md2man -in %{SOURCE14} -out %{buildroot}%{_mandir}/man5/containers.conf.5
 go-md2man -in %{SOURCE15} -out %{buildroot}%{_mandir}/man5/containers-auth.json.5
 go-md2man -in %{SOURCE16} -out %{buildroot}%{_mandir}/man5/containers-registries.conf.d.5
 go-md2man -in %{SOURCE26} -out %{buildroot}%{_mandir}/man5/Containerfile.5
 go-md2man -in %{SOURCE27} -out %{buildroot}%{_mandir}/man5/containerignore.5
 install -dp %{buildroot}%{_datadir}/containers
 install -m0644 %{SOURCE3} %{buildroot}%{_datadir}/containers/mounts.conf
 install -m0644 %{SOURCE7} %{buildroot}%{_datadir}/containers/seccomp.json
 install -m0644 %{SOURCE13} %{buildroot}%{_datadir}/containers/containers.conf
 # install secrets patch directory
 install -d -p -m 755 %{buildroot}/%{_datadir}/rhel/secrets
 # rhbz#1110876 - update symlinks for subscription management
 ln -s %{_sysconfdir}/pki/entitlement %{buildroot}%{_datadir}/rhel/secrets/etc-pki-entitlement
 ln -s %{_sysconfdir}/rhsm %{buildroot}%{_datadir}/rhel/secrets/rhsm
 ln -s %{_sysconfdir}/yum.repos.d/redhat.repo %{buildroot}%{_datadir}/rhel/secrets/redhat.repo
 # ship preconfigured /etc/containers/registries.d/ files with containers-common - #1903813
 cat <<EOF > %{buildroot}%{_sysconfdir}/containers/registries.d/registry.access.redhat.com.yaml
 docker:
     registry.access.redhat.com:
         sigstore: https://access.redhat.com/webassets/docker/content/sigstore
 EOF
 cat <<EOF > %{buildroot}%{_sysconfdir}/containers/registries.d/registry.redhat.io.yaml
 docker:
     registry.redhat.io:
         sigstore: https://registry.redhat.io/containers/sigstore
 EOF
 %files
 %dir %{_sysconfdir}/containers
 %dir %{_sysconfdir}/containers/certs.d
 %dir %{_sysconfdir}/containers/registries.d
 %dir %{_sysconfdir}/containers/oci
 %dir %{_sysconfdir}/containers/oci/hooks.d
 %dir %{_sysconfdir}/containers/registries.conf.d
 %dir %{_sysconfdir}/containers/systemd
 %dir %{_datadir}/containers/systemd
 %if !0%{?rhel} || 0%{?centos}
 %{_sysconfdir}/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
 %{_sysconfdir}/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta
 %endif
 %config(noreplace) %{_sysconfdir}/containers/policy.json
 %config(noreplace) %{_sysconfdir}/containers/storage.conf
 %config(noreplace) %{_sysconfdir}/containers/registries.conf
 %config(noreplace) %{_sysconfdir}/containers/registries.conf.d/*.conf
 %config(noreplace) %{_sysconfdir}/containers/registries.d/default.yaml
 %config(noreplace) %{_sysconfdir}/containers/registries.d/registry.redhat.io.yaml
 %config(noreplace) %{_sysconfdir}/containers/registries.d/registry.access.redhat.com.yaml
 %ghost %{_sysconfdir}/containers/containers.conf
 %dir %{_sharedstatedir}/containers/sigstore
 %{_mandir}/man5/*
 %dir %{_datadir}/containers
 %{_datadir}/containers/mounts.conf
 %{_datadir}/containers/seccomp.json
 %{_datadir}/containers/containers.conf
 %dir %{_datadir}/rhel/secrets
 %{_datadir}/rhel/secrets/*
 %changelog
 * Wed Feb 14 2024 Jindrich Novy <jnovy@redhat.com> - 2:1-81
 - Update shortnames from Pyxis
 - Related: Jira:RHEL-2110
 * Mon Feb 12 2024 Jindrich Novy <jnovy@redhat.com> - 2:1-80
 - bump release to preserve upgrade path
 - Resolves: Jira:RHEL-12277
 * Thu Feb 08 2024 Jindrich Novy <jnovy@redhat.com> - 2:1-59
 - update vendored components
 - Related: Jira:RHEL-2110
 * Tue Jan 02 2024 Jindrich Novy <jnovy@redhat.com> - 2:1-58
 - update vendored components
 - Related: Jira:RHEL-2110
 * Wed Oct 11 2023 Jindrich Novy <jnovy@redhat.com> - 2:1-57
 - fix shortnames for rhel-minimal
 - Related: Jira:RHEL-2110
 * Fri Sep 15 2023 Jindrich Novy <jnovy@redhat.com> - 2:1-56
 - implement GPG auto updating mechanism from redhat-release
 - Resolves: #RHEL-2110
 * Wed Sep 13 2023 Jindrich Novy <jnovy@redhat.com> - 2:1-55
 - update GPG keys to the current content of redhat-release
 - Resolves: #RHEL-3164
 * Fri Aug 25 2023 Jindrich Novy <jnovy@redhat.com> - 2:1-54
 - update vendored components and shortnames
 - Related: #2176055
 * Mon Jul 10 2023 Jindrich Novy <jnovy@redhat.com> - 2:1-53
 - update vendored components
 - Related: #2176055
 * Sat Jul 08 2023 Jindrich Novy <jnovy@redhat.com> - 2:1-52
 - update vendored components
 - Related: #2176055
 * Tue Mar 21 2023 Jindrich Novy <jnovy@redhat.com> - 2:1-51
 - be sure default_capabilities contain SYS_CHROOT
 - Resolves: #2166195
 * Thu Mar 09 2023 Jindrich Novy <jnovy@redhat.com> - 2:1-50
 - improve shortnames generation
 - Related: #2176055
 * Mon Jan 02 2023 Jindrich Novy <jnovy@redhat.com> - 2:1-49
 - update vendored components and configuration files
 - Related: #2123641
 * Fri Dec 02 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-48
 - update vendored components and configuration files
 - Related: #2123641
 * Mon Nov 14 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-47
 - enable NET_RAW capability for RHEL8 only
 - Related: #2123641
 * Tue Nov 08 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-46
 - update vendored components and configuration files
 - Related: #2123641
 * Fri Oct 21 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-45
 - update vendored components and configuration files
 - Related: #2123641
 * Mon Oct 17 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-44
 - update vendored components and configuration files
 - Related: #2123641
 * Thu Oct 06 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-43
 - update vendored components and configuration files
 - Related: #2123641
 * Wed Sep 21 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-42
 - update vendored components and configuration files
 - Related: #2123641
 * Tue Sep 06 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-41
 - add beta GPG key
 - Related: #2123641
 * Tue Aug 23 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-40
 - add beta keys to default-policy.json
 - Related: #2061390
 * Mon Aug 08 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-39
 - update shortnames
 - Related: #2061390
 * Thu Aug 04 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-38
 - arch limitation because of go-md2man (missing on i686)
 - Related: #2061390
 * Wed Aug 03 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-37
 - add install section
 - update vendored components
 - Related: #2061390
 * Wed Aug 03 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-36
 - remove aardvark-dns and netavark - packaged separately
 - update vendored components and configuration files
 - Related: #2061390
 * Tue Jul 26 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-35
 - update vendored components and configuration files
 - Related: #2061390
 * Mon Jun 27 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-34
 - remove rhel-els and update shortnames
 - Related: #2061390
 * Thu Jun 16 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-33
 - update shortnames
 - Related: #2061390
 * Thu Jun 09 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-32
 - additional fix for unqualified registries
 - Related: #2061390
 * Thu Jun 09 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-31
 - fix unqualified registries
 - Related: #2061390
 * Thu Jun 09 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-30
 - update vendored components and configuration files
 - Related: #2061390
 * Mon May 23 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-29
 - update unqualified registries list
 - Related: #2061390
 * Mon May 09 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-28
 - update aardvark-dns and netavark to 1.0.3
 - update vendored components
 - Related: #2061390
 * Fri Apr 22 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-27
 - add man page sources too
 - Related: #2061390
 * Wed Apr 20 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-26
 - add missing man pages from Fedora
 - Related: #2061390
 * Wed Apr 06 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-25
 - allow consuming aardvark-dns and netavark from upstream branch
 - Related: #2061390
 * Wed Apr 06 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-24
 - update to netavark and aardvark-dns 1.0.2
 - update vendored components
 - Related: #2061390
 * Mon Feb 28 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-23
 - update to netavark and aardvark-dns 1.0.1
 - Related: #2001445
 * Wed Feb 23 2022 Lokesh Mandvekar <lsm5@redhat.com> - 2:1-22
 - build rust packages with RUSTFLAGS set to make ExecShield happy
 - Related: #2001445
 * Mon Feb 21 2022 Lokesh Mandvekar <lsm5@redhat.com> - 2:1-21
 - do not specify infra_image in containers.conf
 - needed to resolve gating test failures
 - Related: #2001445
 * Fri Feb 18 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-20
 - update to netavark-1.0.0 and aardvark-dns-1.0.0
 - Related: #2001445
 * Thu Feb 17 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-19
 - package aarvark-dns and netavark as part of the containers-common
 - Related: #2001445
 * Thu Feb 17 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-18
 - update shortnames and vendored components
 - Related: #2001445
 * Wed Feb 16 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-17
 - containers.conf should contain network_backend = "cni" in RHEL8.6
 - Related: #2001445
 * Fri Feb 11 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-16
 - update vendored components and configuration files
 - Related: #2001445
 * Fri Feb 04 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-15
 - sync vendored components
 - Related: #2001445
 * Fri Feb 04 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-14
 - sync vendored components
 - Related: #2001445
 * Mon Jan 17 2022 Jindrich Novy <jnovy@redhat.com> - 2:1-13
 - update shortnames from Pyxis
 - Related: #2001445
 * Thu Dec 09 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-12
 - do not allow broken content from Pyxis to land in shortnames.conf
 - Related: #2001445
 * Wed Dec 08 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-11
 - sync vendored components
 - update shortnames from Pyxis
 - Related: #2001445
 * Wed Dec 01 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-10
 - use log_driver = "journald" and events_logger = "journald" for RHEL9
 - Related: #2001445
 * Tue Nov 16 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-9
 - consume seccomp.json from the oldest vendored version of c/common,
  not main branch
 - Related: #2001445
 * Wed Nov 10 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-8
 - update vendored components
 - Related: #2001445
 * Tue Nov 02 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-7
 - make log_driver = "k8s-file" default in containers.conf
 - Related: #2001445
 * Wed Oct 13 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-6
 - sync vendored components
 - Related: #2001445
 * Wed Sep 29 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-5
 - update to the new vendored components
 - Related: #2001445
 * Fri Sep 24 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-4
 - update to the new vendored components
 - Related: #2001445
 * Fri Sep 10 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-3
 - update to the new vendored components
 - Related: #2001445
 * Wed Aug 11 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-2
 - synchronize config files for RHEL-8.5
 - Related: #1934415
 * Wed Aug 11 2021 Jindrich Novy <jnovy@redhat.com> - 2:1-1
 - initial import
 - Related: #1934415
--- a/SOURCES/containerignore.5.md
+++ b/SOURCES/containerignore.5.md
--- a/SOURCES/containers-auth.json.5.md
+++ b/SOURCES/containers-auth.json.5.md
--- a/SOURCES/containers-certs.d.5.md
+++ b/SOURCES/containers-certs.d.5.md
--- a/containers-common.spec
+++ b/containers-common.spec
@ -0,0 +1,248 @@
 # Below definitions are used to deliver config files from a particular branch
 # of c/image, c/storage  and c/shortnames vendored in all of Buildah, Podman and Skopeo.
 # These vendored components must have the same version. If it is not the case,
 # pick the oldest version on c/image, c/storage and c/shortnames vendored in
 # Buildah/Podman/Skopeo.
 # Packit will automatically update the image and storage versions on Fedora and
 # CentOS Stream dist-git PRs.
 %global skopeo_branch main
 %global image_branch v5.33.0
 %global storage_branch v1.56.0
 %global shortnames_branch main
 %global common_branch v0.61.0
 %global common_version %(v=%{common_branch}; echo ${v:1})
 Name: containers-common
 Epoch: 5
 Version: %{common_version}
 Release: 1%{?dist}
 License: Apache-2.0
 BuildArch: noarch
 # for BuildRequires: go-md2man
 ExclusiveArch: %{golang_arches} noarch
 Summary: Common configuration and documentation for containers
 BuildRequires: git-core
 BuildRequires: go-md2man
 Provides: skopeo-containers = %{epoch}:%{version}-%{release}
 Requires: (container-selinux >= 2:2.162.1 if selinux-policy)
 Requires: netavark
 Obsoletes: containernetworking-plugins < 2
 Suggests: fuse-overlayfs
 %if 0%{?rhel}
 Requires: /etc/pki/sigstore/REKOR-signing-key
 Requires: /etc/pki/sigstore/SIGSTORE-redhat-release3
 %endif
 URL: https://github.com/containers/common
 Source1: https://raw.githubusercontent.com/containers/storage/%{storage_branch}/storage.conf
 Source2: https://raw.githubusercontent.com/containers/storage/%{storage_branch}/docs/containers-storage.conf.5.md
 Source3: mounts.conf
 Source4: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-registries.conf.5.md
 Source5: https://raw.githubusercontent.com/containers/image/%{image_branch}/registries.conf
 Source6: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-policy.json.5.md
 Source7: https://raw.githubusercontent.com/containers/common/%{common_branch}/pkg/seccomp/seccomp.json
 Source8: https://raw.githubusercontent.com/containers/common/%{common_branch}/docs/containers-mounts.conf.5.md
 Source9: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-signature.5.md
 Source10: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-transports.5.md
 Source11: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-certs.d.5.md
 Source12: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-registries.d.5.md
 Source13: https://raw.githubusercontent.com/containers/common/%{common_branch}/pkg/config/containers.conf
 Source14: https://raw.githubusercontent.com/containers/common/%{common_branch}/docs/containers.conf.5.md
 Source15: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-auth.json.5.md
 Source16: https://raw.githubusercontent.com/containers/image/%{image_branch}/docs/containers-registries.conf.d.5.md
 Source17: https://raw.githubusercontent.com/containers/shortnames/%{shortnames_branch}/shortnames.conf
 Source19: 001-rhel-shortnames-pyxis.conf
 Source20: 002-rhel-shortnames-overrides.conf
 Source22: registry.access.redhat.com.yaml
 Source23: registry.redhat.io.yaml
 #Source24: https://raw.githubusercontent.com/containers/skopeo/%%{skopeo_branch}/default-policy.json
 Source24: default-policy.json
 Source25: https://raw.githubusercontent.com/containers/skopeo/%{skopeo_branch}/default.yaml
 # FIXME: fix the branch once these are available via regular c/common branch
 Source26: https://raw.githubusercontent.com/containers/common/main/docs/Containerfile.5.md
 Source27: https://raw.githubusercontent.com/containers/common/main/docs/containerignore.5.md
 Source29: REKOR-signing-key
 Source30: SIGSTORE-redhat-release3
 # scripts used for synchronization with upstream and shortname generation
 Source100: update.sh
 Source101: update-vendored.sh
 Source102: pyxis.sh
 %description
 This package contains common configuration files and documentation for container
 tools ecosystem, such as Podman, Buildah and Skopeo.
 It is required because the most of configuration files and docs come from projects
 which are vendored into Podman, Buildah, Skopeo, etc. but they are not packaged
 separately.
 %package extra
 Summary: Extra dependencies for Podman and Buildah
 Requires: %{name} = %{epoch}:%{version}-%{release}
 Requires: container-network-stack
 Requires: oci-runtime
 Requires: nftables
 Requires: passt
 %description extra
 This subpackage will handle dependencies common to Podman and Buildah which are
 not required by Skopeo.
 %prep
 %build
 %install
 install -dp %{buildroot}%{_sysconfdir}/containers/{certs.d,oci/hooks.d,systemd,registries.d,registries.conf.d}
 install -dp %{buildroot}%{_datadir}/containers/systemd
 install -dp %{buildroot}%{_sharedstatedir}/containers/sigstore
 install -dp %{buildroot}%{_prefix}/lib/containers/storage
 install -dp -m 700 %{buildroot}%{_prefix}/lib/containers/storage/overlay-images
 touch %{buildroot}%{_prefix}/lib/containers/storage/overlay-images/images.lock
 install -dp -m 700 %{buildroot}%{_prefix}/lib/containers/storage/overlay-layers
 touch %{buildroot}%{_prefix}/lib/containers/storage/overlay-layers/layers.lock
 install -m0644 %{SOURCE1} %{buildroot}%{_datadir}/containers/storage.conf
 install -m0644 %{SOURCE5} %{buildroot}%{_sysconfdir}/containers/registries.conf
 install -m0644 %{SOURCE17} %{buildroot}%{_sysconfdir}/containers/registries.conf.d/000-shortnames.conf
 install -m0644 %{SOURCE19} %{buildroot}%{_sysconfdir}/containers/registries.conf.d/001-rhel-shortnames.conf
 install -m0644 %{SOURCE20} %{buildroot}%{_sysconfdir}/containers/registries.conf.d/002-rhel-shortnames-overrides.conf
 install -dp %{buildroot}%{_sysconfdir}/containers/registries.d
 install -m0644 %{SOURCE22} %{buildroot}%{_sysconfdir}/containers/registries.d
 install -m0644 %{SOURCE23} %{buildroot}%{_sysconfdir}/containers/registries.d
 install -m0644 %{SOURCE24} %{buildroot}%{_sysconfdir}/containers/policy.json
 install -dp %{buildroot}%{_sharedstatedir}/containers/sigstore
 install -m0644 %{SOURCE25} %{buildroot}%{_sysconfdir}/containers/registries.d/default.yaml
 # for containers-common
 install -dp %{buildroot}%{_mandir}/man5
 go-md2man -in %{SOURCE2} -out %{buildroot}%{_mandir}/man5/containers-storage.conf.5
 go-md2man -in %{SOURCE4} -out %{buildroot}%{_mandir}/man5/containers-registries.conf.5
 go-md2man -in %{SOURCE6} -out %{buildroot}%{_mandir}/man5/containers-policy.json.5
 go-md2man -in %{SOURCE8} -out %{buildroot}%{_mandir}/man5/containers-mounts.conf.5
 go-md2man -in %{SOURCE9} -out %{buildroot}%{_mandir}/man5/containers-signature.5
 go-md2man -in %{SOURCE10} -out %{buildroot}%{_mandir}/man5/containers-transports.5
 go-md2man -in %{SOURCE11} -out %{buildroot}%{_mandir}/man5/containers-certs.d.5
 go-md2man -in %{SOURCE12} -out %{buildroot}%{_mandir}/man5/containers-registries.d.5
 go-md2man -in %{SOURCE14} -out %{buildroot}%{_mandir}/man5/containers.conf.5
 go-md2man -in %{SOURCE15} -out %{buildroot}%{_mandir}/man5/containers-auth.json.5
 go-md2man -in %{SOURCE16} -out %{buildroot}%{_mandir}/man5/containers-registries.conf.d.5
 go-md2man -in %{SOURCE26} -out %{buildroot}%{_mandir}/man5/Containerfile.5
 go-md2man -in %{SOURCE27} -out %{buildroot}%{_mandir}/man5/containerignore.5
 ln -s containerignore.5 %{buildroot}%{_mandir}/man5/.containerignore.5
 install -dp %{buildroot}%{_datadir}/containers
 install -m0644 %{SOURCE3} %{buildroot}%{_datadir}/containers/mounts.conf
 install -m0644 %{SOURCE7} %{buildroot}%{_datadir}/containers/seccomp.json
 install -m0644 %{SOURCE13} %{buildroot}%{_datadir}/containers/containers.conf
 # for signature verification
 %if 0%{?fedora} || 0%{?centos}
 install -dp %{buildroot}%{_sysconfdir}/pki/sigstore
 install -m0644 %{SOURCE29} %{buildroot}%{_sysconfdir}/pki/sigstore
 install -m0644 %{SOURCE30} %{buildroot}%{_sysconfdir}/pki/sigstore
 %endif
 # install secrets patch directory
 install -d -p -m 755 %{buildroot}/%{_datadir}/rhel/secrets
 # rhbz#1110876 - update symlinks for subscription management
 ln -s ../../../..%{_sysconfdir}/pki/entitlement %{buildroot}%{_datadir}/rhel/secrets/etc-pki-entitlement
 ln -s ../../../..%{_sysconfdir}/rhsm %{buildroot}%{_datadir}/rhel/secrets/rhsm
 ln -s ../../../..%{_sysconfdir}/yum.repos.d/redhat.repo %{buildroot}%{_datadir}/rhel/secrets/redhat.repo
 %files
 %dir %{_sysconfdir}/containers
 %dir %{_sysconfdir}/containers/certs.d
 %dir %{_sysconfdir}/containers/oci
 %dir %{_sysconfdir}/containers/oci/hooks.d
 %dir %{_sysconfdir}/containers/registries.conf.d
 %dir %{_sysconfdir}/containers/registries.d
 %dir %{_sysconfdir}/containers/systemd
 %dir %{_prefix}/lib/containers
 %dir %{_prefix}/lib/containers/storage
 %dir %{_prefix}/lib/containers/storage/overlay-images
 %dir %{_prefix}/lib/containers/storage/overlay-layers
 %{_prefix}/lib/containers/storage/overlay-images/images.lock
 %{_prefix}/lib/containers/storage/overlay-layers/layers.lock
 %config(noreplace) %{_sysconfdir}/containers/policy.json
 %config(noreplace) %{_sysconfdir}/containers/registries.conf
 %config(noreplace) %{_sysconfdir}/containers/registries.conf.d/*.conf
 %if 0%{?fedora} || 0%{?centos}
 %{_sysconfdir}/pki/sigstore/REKOR-signing-key
 %{_sysconfdir}/pki/sigstore/SIGSTORE-redhat-release3
 %endif
 %config(noreplace) %{_sysconfdir}/containers/registries.d/default.yaml
 %config(noreplace) %{_sysconfdir}/containers/registries.d/registry.redhat.io.yaml
 %config(noreplace) %{_sysconfdir}/containers/registries.d/registry.access.redhat.com.yaml
 %ghost %{_sysconfdir}/containers/storage.conf
 %ghost %{_sysconfdir}/containers/containers.conf
 %dir %{_sharedstatedir}/containers/sigstore
 %{_mandir}/man5/Containerfile.5.gz
 %{_mandir}/man5/containerignore.5.gz
 %{_mandir}/man5/.containerignore.5.gz
 %{_mandir}/man5/containers*.5.gz
 %dir %{_datadir}/containers
 %dir %{_datadir}/containers/systemd
 %{_datadir}/containers/storage.conf
 %{_datadir}/containers/containers.conf
 %{_datadir}/containers/mounts.conf
 %{_datadir}/containers/seccomp.json
 %dir %{_datadir}/rhel
 %dir %{_datadir}/rhel/secrets
 %{_datadir}/rhel/secrets/*
 %files extra
 %changelog
 * Mon Dec 16 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.61.0-1
 - make spec file compatible with RHEL
 - update vendored components
 - Resolves: RHEL-69842
 * Tue Nov 26 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.60.2-13
 - update vendored components
 - Related: RHEL-58990
 * Mon Nov 25 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.60.2-12
 - Use proper log_driver: k8s-file
 - Resolves: RHEL-68081
 * Thu Oct 31 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.60.2-11
 - Install shortnames from Pyxis and overrides
 - Resolves: RHEL-34940
 * Wed Oct 30 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.60.2-10
 - don't use registry yaml files from upstream but RHEL10 dedicated ones
 - Resolves: RHEL-65203
 * Wed Oct 30 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.60.2-9
 - ensure required configurations for RHEL10 is present
 - Resolves: RHEL-58990
 * Tue Oct 29 2024 Troy Dawson <tdawson@redhat.com> - 5:0.60.2-8
 - Bump release for October 2024 mass rebuild:
  Resolves: RHEL-64018
 * Tue Oct 29 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.60.2-7
 - Enable sigstore support
 - Resolves: RUN-2164
 * Tue Sep 10 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.60.2-6
 - package GPG keys only on Fedora and CentOS
 - Related: RHEL-39410
 * Mon Sep 09 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.60.2-5
 - include relevant GPG keys
 - Resolves: RHEL-57720
 * Thu Sep 05 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.60.2-4
 - update update.sh script and set logdriver to file
 - Resolves: RHEL-57101
 * Wed Aug 28 2024 Jindrich Novy <jnovy@redhat.com> - 5:0.60.2-3
 - Obsolete containernetworking-plugins
 - Resolves: RHEL-39410
--- a/containers-containerfile.5.md
+++ b/containers-containerfile.5.md
@ -0,0 +1,507 @@
 % "CONTAINERFILE" "5" "Aug 2021" "" "Container User Manuals"
 # NAME
 Containerfile(Dockerfile) - automate the steps of creating a container image
 # INTRODUCTION
 The **Containerfile** is a configuration file that automates the steps of creating a container image. It is similar to a Makefile. Container engines (Podman, Buildah, Docker) read instructions from the **Containerfile** to automate the steps otherwise performed manually to create an image. To build an image, create a file called **Containerfile**.
 The **Containerfile** describes the steps taken to assemble the image. When the
 **Containerfile** has been created, call the `buildah bud`, `podman build`, `docker build` command,
 using the path of context directory that contains **Containerfile** as the argument. Podman and Buildah default to **Containerfile** and will fall back to **Dockerfile**. Docker only will search for **Dockerfile** in the context directory.
 **Dockerfile** is an alternate name for the same object.  **Containerfile** and **Dockerfile** support the same syntax.
 # SYNOPSIS
 INSTRUCTION arguments
 For example:
  FROM image
 # DESCRIPTION
 A Containerfile is a file that automates the steps of creating a container image.
 A Containerfile is similar to a Makefile.
 # USAGE
  ```
  buildah bud .
  podman build .
  ```
  -- Runs the steps and commits them, building a final image.
  The path to the source repository defines where to find the context of the
  build.
  ```
  buildah bud -t repository/tag .
  podman build -t repository/tag .
  ```
  -- specifies a repository and tag at which to save the new image if the build
  succeeds. The container engine runs the steps one-by-one, committing the result
  to a new image if necessary, before finally outputting the ID of the new
  image.
  Container engines re-use intermediate images whenever possible. This significantly
  accelerates the *build* process.
 # FORMAT
  `FROM image`
  `FROM image:tag`
  `FROM image@digest`
  -- The **FROM** instruction sets the base image for subsequent instructions. A
  valid Containerfile must have **FROM** as its first instruction. The image can be any
  valid image. It is easy to start by pulling an image from the public
  repositories.
  -- **FROM** must be the first non-comment instruction in Containerfile.
  -- **FROM** may appear multiple times within a single Containerfile in order to create
  multiple images. Make a note of the last image ID output by the commit before
  each new **FROM** command.
  -- If no tag is given to the **FROM** instruction, container engines apply the
  `latest` tag. If the used tag does not exist, an error is returned.
  -- If no digest is given to the **FROM** instruction, container engines apply the
  `latest` tag. If the used tag does not exist, an error is returned.
 **MAINTAINER**
  -- **MAINTAINER** sets the Author field for the generated images.
  Useful for providing users with an email or url for support.
 **RUN**
  -- **RUN** has two forms:
  ```
  # the command is run in a shell - /bin/sh -c
  RUN <command>
  # Executable form
  RUN ["executable", "param1", "param2"]
  ```
 **RUN Secrets*
 The RUN command has a feature to allow the passing of secret information into the image build. These secrets files can be used during the RUN command but are not committed to the final image. The `RUN` command supports the `--mount` option to identify the secret file. A secret file from the host is mounted into the container while the image is being built.
 Container engines pass secret the secret file into the build using the `--secret` flag.
 **RUN --mount* options:
 - `id` is the identifier to for the secret passed into the `buildah bud --secret` or `podman build --secret`. This identifier is associated with the RUN --mount identifier to use in the Containerfile.
 - `dst`|`target`|`destination` rename the secret file to a specific file in the Containerfile RUN command to use.
 - `type=secret` tells the --mount command that it is mounting in a secret file
 # shows secret from default secret location:
 RUN --mount=type=secret,id=mysecret cat /run/secrets/mysecret
 # shows secret from custom secret location:
 RUN --mount=type=secret,id=mysecret,dst=/foobar cat /foobar
 The secret needs to be passed to the build using the --secret flag. The final image built does not container the secret file:
 ```
 buildah bud --no-cache --secret id=mysecret,src=mysecret.txt .
 ```
  -- The **RUN** instruction executes any commands in a new layer on top of the current
  image and commits the results. The committed image is used for the next step in
  Containerfile.
  -- Layering **RUN** instructions and generating commits conforms to the core
  concepts of container engines where commits are cheap and containers can be created from
  any point in the history of an image. This is similar to source control.  The
  exec form makes it possible to avoid shell string munging. The exec form makes
  it possible to **RUN** commands using a base image that does not contain `/bin/sh`.
  Note that the exec form is parsed as a JSON array, which means that you must
  use double-quotes (") around words not single-quotes (').
 **CMD**
  -- **CMD** has three forms:
  ```
  # Executable form
  CMD ["executable", "param1", "param2"]`
  # Provide default arguments to ENTRYPOINT
  CMD ["param1", "param2"]`
  # the command is run in a shell - /bin/sh -c
  CMD command param1 param2
  ```
  -- There should be only one **CMD** in a Containerfile. If more than one **CMD** is listed, only
  the last **CMD** takes effect.
  The main purpose of a **CMD** is to provide defaults for an executing container.
  These defaults may include an executable, or they can omit the executable. If
  they omit the executable, an **ENTRYPOINT** must be specified.
  When used in the shell or exec formats, the **CMD** instruction sets the command to
  be executed when running the image.
  If you use the shell form of the **CMD**, the `<command>` executes in `/bin/sh -c`:
  Note that the exec form is parsed as a JSON array, which means that you must
  use double-quotes (") around words not single-quotes (').
  ```
  FROM ubuntu
  CMD echo "This is a test." | wc -
  ```
  -- If you run **command** without a shell, then you must express the command as a
  JSON array and give the full path to the executable. This array form is the
  preferred form of **CMD**. All additional parameters must be individually expressed
  as strings in the array:
  ```
  FROM ubuntu
  CMD ["/usr/bin/wc","--help"]
  ```
  -- To make the container run the same executable every time, use **ENTRYPOINT** in
  combination with **CMD**.
  If the user specifies arguments to `podman run` or `docker run`, the specified commands
  override the default in **CMD**.
  Do not confuse **RUN** with **CMD**. **RUN** runs a command and commits the result.
  **CMD** executes nothing at build time, but specifies the intended command for
  the image.
 **LABEL**
  -- `LABEL <key>=<value> [<key>=<value> ...]`or
  ```
  LABEL <key>[ <value>]
  LABEL <key>[ <value>]
  ...
  ```
  The **LABEL** instruction adds metadata to an image. A **LABEL** is a
  key-value pair. To specify a **LABEL** without a value, simply use an empty
  string. To include spaces within a **LABEL** value, use quotes and
  backslashes as you would in command-line parsing.
  ```
  LABEL com.example.vendor="ACME Incorporated"
  LABEL com.example.vendor "ACME Incorporated"
  LABEL com.example.vendor.is-beta ""
  LABEL com.example.vendor.is-beta=
  LABEL com.example.vendor.is-beta=""
  ```
  An image can have more than one label. To specify multiple labels, separate
  each key-value pair by a space.
  Labels are additive including `LABEL`s in `FROM` images. As the system
  encounters and then applies a new label, new `key`s override any previous
  labels with identical keys.
  To display an image's labels, use the `buildah inspect` command.
 **EXPOSE**
  -- `EXPOSE <port> [<port>...]`
  The **EXPOSE** instruction informs the container engine that the container listens on the
  specified network ports at runtime. The container engine uses this information to
  interconnect containers using links and to set up port redirection on the host
  system.
 **ENV**
  -- `ENV <key> <value>`
  The **ENV** instruction sets the environment variable <key> to
  the value `<value>`. This value is passed to all future
  **RUN**, **ENTRYPOINT**, and **CMD** instructions. This is
  functionally equivalent to prefixing the command with `<key>=<value>`.  The
  environment variables that are set with **ENV** persist when a container is run
  from the resulting image. Use `podman inspect` to inspect these values, and
  change them using `podman run --env <key>=<value>`.
  Note that setting "`ENV DEBIAN_FRONTEND=noninteractive`" may cause
  unintended consequences, because it will persist when the container is run
  interactively, as with the following command: `podman run -t -i image bash`
 **ADD**
  -- **ADD** has two forms:
  ```
  ADD <src> <dest>
  # Required for paths with whitespace
  ADD ["<src>",... "<dest>"]
  ```
  The **ADD** instruction copies new files, directories
  or remote file URLs to the filesystem of the container at path `<dest>`.
  Multiple `<src>` resources may be specified but if they are files or directories
  then they must be relative to the source directory that is being built
  (the context of the build). The `<dest>` is the absolute path, or path relative
  to **WORKDIR**, into which the source is copied inside the target container.
  If the `<src>` argument is a local file in a recognized compression format
  (tar, gzip, bzip2, etc) then it is unpacked at the specified `<dest>` in the
  container's filesystem.  Note that only local compressed files will be unpacked,
  i.e., the URL download and archive unpacking features cannot be used together.
  All new directories are created with mode 0755 and with the uid and gid of **0**.
 **COPY**
  -- **COPY** has two forms:
  ```
  COPY <src> <dest>
  # Required for paths with whitespace
  COPY ["<src>",... "<dest>"]
  ```
  The **COPY** instruction copies new files from `<src>` and
  adds them to the filesystem of the container at path `<dest>`. The `<src>` must be
  the path to a file or directory relative to the source directory that is
  being built (the context of the build) or a remote file URL. The `<dest>` is an
  absolute path, or a path relative to **WORKDIR**, into which the source will
  be copied inside the target container. If you **COPY** an archive file it will
  land in the container exactly as it appears in the build context without any
  attempt to unpack it.  All new files and directories are created with mode **0755**
  and with the uid and gid of **0**.
 **ENTRYPOINT**
  -- **ENTRYPOINT** has two forms:
  ```
  # executable form
  ENTRYPOINT ["executable", "param1", "param2"]`
  # run command in a shell - /bin/sh -c
  ENTRYPOINT command param1 param2
  ```
  -- An **ENTRYPOINT** helps you configure a
  container that can be run as an executable. When you specify an **ENTRYPOINT**,
  the whole container runs as if it was only that executable.  The **ENTRYPOINT**
  instruction adds an entry command that is not overwritten when arguments are
  passed to `podman run`. This is different from the behavior of **CMD**. This allows
  arguments to be passed to the entrypoint, for instance `podman run <image> -d`
  passes the -d argument to the **ENTRYPOINT**.  Specify parameters either in the
  **ENTRYPOINT** JSON array (as in the preferred exec form above), or by using a **CMD**
  statement.  Parameters in the **ENTRYPOINT** are not overwritten by the `podman run` arguments.  Parameters specified via **CMD** are overwritten by `podman run` arguments.  Specify a plain string for the **ENTRYPOINT**, and it will execute in
  `/bin/sh -c`, like a **CMD** instruction:
  ```
  FROM ubuntu
  ENTRYPOINT wc -l -
  ```
  This means that the Containerfile's image always takes stdin as input (that's
  what "-" means), and prints the number of lines (that's what "-l" means). To
  make this optional but default, use a **CMD**:
  ```
  FROM ubuntu
  CMD ["-l", "-"]
  ENTRYPOINT ["/usr/bin/wc"]
  ```
 **VOLUME**
  -- `VOLUME ["/data"]`
  The **VOLUME** instruction creates a mount point with the specified name and marks
  it as holding externally-mounted volumes from the native host or from other
  containers.
 **USER**
  -- `USER daemon`
  Sets the username or UID used for running subsequent commands.
  The **USER** instruction can optionally be used to set the group or GID. The
  following examples are all valid:
  USER [user | user:group | uid | uid:gid | user:gid | uid:group ]
  Until the **USER** instruction is set, instructions will be run as root. The USER
  instruction can be used any number of times in a Containerfile, and will only affect
  subsequent commands.
 **WORKDIR**
  -- `WORKDIR /path/to/workdir`
  The **WORKDIR** instruction sets the working directory for the **RUN**, **CMD**,
  **ENTRYPOINT**, **COPY** and **ADD** Containerfile commands that follow it. It can
  be used multiple times in a single Containerfile. Relative paths are defined
  relative to the path of the previous **WORKDIR** instruction. For example:
  ```
  WORKDIR /a
  WORKDIR b
  WORKDIR c
  RUN pwd
  ```
  In the above example, the output of the **pwd** command is **a/b/c**.
 **ARG**
   -- ARG <name>[=<default value>]
  The `ARG` instruction defines a variable that users can pass at build-time to
  the builder with the `podman build` command using the `--build-arg
  <varname>=<value>` flag. If a user specifies a build argument that was not
  defined in the Containerfile, the build outputs a warning.
  ```
  [Warning] One or more build-args [foo] were not consumed
  ```
  The Containerfile author can define a single variable by specifying `ARG` once or many
  variables by specifying `ARG` more than once. For example, a valid Containerfile:
  ```
  FROM busybox
  ARG user1
  ARG buildno
  ...
  ```
  A Containerfile author may optionally specify a default value for an `ARG` instruction:
  ```
  FROM busybox
  ARG user1=someuser
  ARG buildno=1
  ...
  ```
  If an `ARG` value has a default and if there is no value passed at build-time, the
  builder uses the default.
  An `ARG` variable definition comes into effect from the line on which it is
  defined in the `Containerfile` not from the argument's use on the command-line or
  elsewhere.  For example, consider this Containerfile:
  ```
  1 FROM busybox
  2 USER ${user:-some_user}
  3 ARG user
  4 USER $user
  ...
  ```
  A user builds this file by calling:
  ```
  $ podman build --build-arg user=what_user Containerfile
  ```
  The `USER` at line 2 evaluates to `some_user` as the `user` variable is defined on the
  subsequent line 3. The `USER` at line 4 evaluates to `what_user` as `user` is
  defined and the `what_user` value was passed on the command line. Prior to its definition by an
  `ARG` instruction, any use of a variable results in an empty string.
  > **Warning:** It is not recommended to use build-time variables for
  >  passing secrets like github keys, user credentials etc. Build-time variable
  >  values are visible to any user of the image with the `podman history` command.
  You can use an `ARG` or an `ENV` instruction to specify variables that are
  available to the `RUN` instruction. Environment variables defined using the
  `ENV` instruction always override an `ARG` instruction of the same name. Consider
  this Containerfile with an `ENV` and `ARG` instruction.
  ```
  1 FROM ubuntu
  2 ARG CONT_IMG_VER
  3 ENV CONT_IMG_VER=v1.0.0
  4 RUN echo $CONT_IMG_VER
  ```
  Then, assume this image is built with this command:
  ```
  $ podman build --build-arg CONT_IMG_VER=v2.0.1 Containerfile
  ```
  In this case, the `RUN` instruction uses `v1.0.0` instead of the `ARG` setting
  passed by the user:`v2.0.1` This behavior is similar to a shell
  script where a locally scoped variable overrides the variables passed as
  arguments or inherited from environment, from its point of definition.
  Using the example above but a different `ENV` specification you can create more
  useful interactions between `ARG` and `ENV` instructions:
  ```
  1 FROM ubuntu
  2 ARG CONT_IMG_VER
  3 ENV CONT_IMG_VER=${CONT_IMG_VER:-v1.0.0}
  4 RUN echo $CONT_IMG_VER
  ```
  Unlike an `ARG` instruction, `ENV` values are always persisted in the built
  image. Consider a `podman build` without the --build-arg flag:
  ```
  $ podman build Containerfile
  ```
  Using this Containerfile example, `CONT_IMG_VER` is still persisted in the image but
  its value would be `v1.0.0` as it is the default set in line 3 by the `ENV` instruction.
  The variable expansion technique in this example allows you to pass arguments
  from the command line and persist them in the final image by leveraging the
  `ENV` instruction. Variable expansion is only supported for [a limited set of
  Containerfile instructions.](#environment-replacement)
  Container engines have a set of predefined `ARG` variables that you can use without a
  corresponding `ARG` instruction in the Containerfile.
  * `HTTP_PROXY`
  * `http_proxy`
  * `HTTPS_PROXY`
  * `https_proxy`
  * `FTP_PROXY`
  * `ftp_proxy`
  * `NO_PROXY`
  * `no_proxy`
  * `ALL_PROXY`
  * `all_proxy`
  To use these, pass them on the command line using `--build-arg` flag, for
  example:
  ```
  $ podman build --build-arg HTTPS_PROXY=https://my-proxy.example.com .
  ```
 **ONBUILD**
  -- `ONBUILD [INSTRUCTION]`
  The **ONBUILD** instruction adds a trigger instruction to an image. The
  trigger is executed at a later time, when the image is used as the base for
  another build. Container engines execute the trigger in the context of the downstream
  build, as if the trigger existed immediately after the **FROM** instruction in
  the downstream Containerfile.
  You can register any build instruction as a trigger. A trigger is useful if
  you are defining an image to use as a base for building other images. For
  example, if you are defining an application build environment or a daemon that
  is customized with a user-specific configuration.
  Consider an image intended as a reusable python application builder. It must
  add application source code to a particular directory, and might need a build
  script called after that. You can't just call **ADD** and **RUN** now, because
  you don't yet have access to the application source code, and it is different
  for each application build.
  -- Providing application developers with a boilerplate Containerfile to copy-paste
  into their application is inefficient, error-prone, and
  difficult to update because it mixes with application-specific code.
  The solution is to use **ONBUILD** to register instructions in advance, to
  run later, during the next build stage.
 ## SEE ALSO
 buildah(1), podman(1), docker(1)
 # HISTORY
 *May 2014, Compiled by Zac Dover (zdover at redhat dot com) based on docker.com Dockerfile documentation.
 *Feb 2015, updated by Brian Goff (cpuguy83@gmail.com) for readability
 *Sept 2015, updated by Sally O'Malley (somalley@redhat.com)
 *Oct 2016, updated by Addam Hardy (addam.hardy@gmail.com)
 *Aug 2021, converted Dockerfile man page to Containerfile by Dan Walsh (dwalsh@redhat.com)
--- a/SOURCES/containers-mounts.conf.5.md
+++ b/SOURCES/containers-mounts.conf.5.md
--- a/SOURCES/containers-policy.json.5.md
+++ b/SOURCES/containers-policy.json.5.md
@ -320,7 +320,9 @@ This requirement requires an image to be signed using a sigstore signature with
 {
    "type":    "sigstoreSigned",
    "keyPath": "/path/to/local/public/key/file",
    "keyPaths": ["/path/to/first/public/key/one", "/path/to/first/public/key/two"],
    "keyData": "base64-encoded-public-key-data",
    "keyDatas": ["base64-encoded-public-key-one-data", "base64-encoded-public-key-two-data"]
    "fulcio": {
        "caPath": "/path/to/local/CA/file",
        "caData": "base64-encoded-CA-data",
@ -328,28 +330,33 @@ This requirement requires an image to be signed using a sigstore signature with
        "subjectEmail", "expected-signing-user@example.com",
    },
    "rekorPublicKeyPath": "/path/to/local/public/key/file",
    "rekorPublicKeyPaths": ["/path/to/local/public/key/one","/path/to/local/public/key/two"],
    "rekorPublicKeyData": "base64-encoded-public-key-data",
    "rekorPublicKeyDatas": ["base64-encoded-public-key-one-data","base64-encoded-public-key-two-data"],
    "signedIdentity": identity_requirement
 }
 ```
-Exactly one of `keyPath`, `keyData` and `fulcio` must be present.
+Exactly one of `keyPath`, `keyPaths`, `keyData`, `keyDatas` and `fulcio` must be present.
 If `keyPath` or `keyData` is present, it contains a sigstore public key.
 Only signatures made by this key are accepted.
 If `keyPaths` or `keyDatas` is present, it contains sigstore public keys.
 Only signatures made by any key in the list are accepted.
 If `fulcio` is present, the signature must be based on a Fulcio-issued certificate.
 One of `caPath` and `caData` must be specified, containing the public key of the Fulcio instance.
 Both `oidcIssuer` and `subjectEmail` are mandatory,
 exactly specifying the expected identity provider,
 and the identity of the user obtaining the Fulcio certificate.
-At most one of `rekorPublicKeyPath` and `rekorPublicKeyData` can be present;
+At most one of `rekorPublicKeyPath`, `rekorPublicKeyPaths`, `rekorPublicKeyData` and `rekorPublicKeyDatas` can be present;
 it is mandatory if `fulcio` is specified.
 If a Rekor public key is specified,
 the signature must have been uploaded to a Rekor server
 and the signature must contain an (offline-verifiable) “signed entry timestamp”
 proving the existence of the Rekor log record,
-signed by the provided public key.
+signed by one of the provided public keys.
 The `signedIdentity` field has the same semantics as in the `signedBy` requirement described above.
 Note that `cosign`-created signatures only contain a repository, so only `matchRepository` and `exactRepository` can be used to accept them (and that does not protect against substitution of a signed image with an unexpected tag).
--- a/SOURCES/containers-registries.conf.5.md
+++ b/SOURCES/containers-registries.conf.5.md
@ -19,6 +19,12 @@ Container engines will use the `$HOME/.config/containers/registries.conf` if it
 `credential-helpers`
 : An array of default credential helpers used as external credential stores.  Note that "containers-auth.json" is a reserved value to use auth files as specified in containers-auth.json(5).  The credential helpers are set to `["containers-auth.json"]` if none are specified.
 `additional-layer-store-auth-helper`
 : A string containing the helper binary name. This enables passing registry credentials to an
  Additional Layer Store every time an image is read using the `docker://`
  transport so that it can access private registries. See the 'Enabling Additional Layer Store to access to private registries' section below for
  more details.
 ### NAMESPACED `[[registry]]` SETTINGS
 The bulk of the configuration is represented as an array of `[[registry]]`
@ -254,6 +260,30 @@ in order, and use the first one that exists.
 Note that a mirror is associated only with the current `[[registry]]` TOML table. If using the example above, pulling the image `registry.com/image:latest` will hence only reach out to `mirror.registry.com`, and the mirrors associated with `example.com/foo` will not be considered.
 ### Enabling Additional Layer Store to access to private registries
 The `additional-layer-store-auth-helper` option enables passing registry
 credentials to an Additional Layer Store so that it can access private registries.
 When accessing a private registry via an Additional Layer Store, a helper binary needs to be provided. This helper binary is
 registered via the `additional-layer-store-auth-helper` option. Every time an image
 is read using the `docker://` transport, the specified helper binary is executed
 and receives registry credentials from stdin in the following format.
 ```json
 {
  "$image_reference": {
    "username": "$username",
    "password": "$password",
    "identityToken": "$identityToken"
  }
 }
 ```
 The format of `$image_reference` is `$repo{:$tag|@$digest}`.
 Additional Layer Stores can use this helper binary to access the private registry.
 ## VERSION 1 FORMAT - DEPRECATED
 VERSION 1 format is still supported but it does not support
 using registry mirrors, longest-prefix matches, or location rewriting.
--- a/SOURCES/containers-registries.conf.d.5.md
+++ b/SOURCES/containers-registries.conf.d.5.md
--- a/SOURCES/containers-registries.d.5.md
+++ b/SOURCES/containers-registries.d.5.md
--- a/SOURCES/containers-signature.5.md
+++ b/SOURCES/containers-signature.5.md
--- a/SOURCES/containers-storage.conf.5.md
+++ b/SOURCES/containers-storage.conf.5.md
@ -27,7 +27,7 @@ No bare options are used. The format of TOML can be simplified to:
 The `storage` table supports the following options:
 **driver**=""
-  Copy On Write (COW) container storage driver. Valid drivers are "overlay", "vfs", "devmapper", "aufs", "btrfs", and "zfs". Some drivers (for example, "zfs", "btrfs", and "aufs") may not work if your kernel lacks support for the filesystem.
+  Copy On Write (COW) container storage driver. Valid drivers are "overlay", "vfs", "aufs", "btrfs", and "zfs". Some drivers (for example, "zfs", "btrfs", and "aufs") may not work if your kernel lacks support for the filesystem.
 This field is required to guarantee proper operation.
 Valid rootless drivers are "btrfs", "overlay", and "vfs".
 Rootless users default to the driver defined in the system configuration when possible.
@ -71,7 +71,7 @@ Default directory to store all temporary writable content created by container s
 By default, the storage driver is set via the `driver` option. If it is not defined, then the best driver will be picked according to the current platform. This option allows you to override this internal priority list with a custom one to prefer certain drivers.
 Setting this option only has an effect if the local storage has not been initialized yet and the driver name is not set.
-**transient_store** = "false" | "true"
+**transient_store** = "false"|"true"
 Transient store mode makes all container metadata be saved in temporary storage
 (i.e. runroot above). This is faster, but doesn't persist across reboots.
@ -84,51 +84,6 @@ The `storage.options` table supports the following options:
 **additionalimagestores**=[]
  Paths to additional container image stores. Usually these are read/only and stored on remote network shares.
 **pull_options** = {enable_partial_images = "false", use_hard_links = "false", ostree_repos=""}
 Allows specification of how storage is populated when pulling images. This
 option can speed the pulling process of images compressed with format zstd:chunked. Containers/storage looks
 for files within images that are being pulled from a container registry that
 were previously pulled to the host.  It can copy or create
 a hard link to the existing file when it finds them, eliminating the need to pull them from the
 container registry. These options can deduplicate pulling of content, disk
 storage of content and can allow the kernel to use less memory when running
 containers.
 containers/storage supports three keys
  * enable_partial_images="true" | "false"
    Tells containers/storage to look for files previously pulled in storage
    rather then always pulling them from the container registry.
  * use_hard_links = "false" | "true"
    Tells containers/storage to use hard links rather then create new files in
    the image, if an identical file already existed in storage.
  * ostree_repos = ""
    Tells containers/storage where an ostree repository exists that might have
    previously pulled content which can be used when attempting to avoid
    pulling content from the container registry
  * convert_images = "false" | "true"
    If set to true, containers/storage will convert images to the a format compatible with
    partial pulls in order to take advantage of local deduplication and hardlinking.  It is an
    expensive operation so it is not enabled by default.
 **remap-uids=**""
 **remap-gids=**""
  Remap-UIDs/GIDs is the mapping from UIDs/GIDs as they should appear inside of a container, to the UIDs/GIDs outside of the container, and the length of the range of UIDs/GIDs.  Additional mapped sets can be listed and will be heeded by libraries, but there are limits to the number of mappings which the kernel will allow when you later attempt to run a container.
  Example
     remap-uids = "0:1668442479:65536"
     remap-gids = "0:1668442479:65536"
  These mappings tell the container engines to map UID 0 inside of the container to UID 1668442479 outside.  UID 1 will be mapped to 1668442480. UID 2 will be mapped to 1668442481, etc, for the next 65533 UIDs in succession.
 **remap-user**=""
 **remap-group**=""
  Remap-User/Group is a user name which can be used to look up one or more UID/GID ranges in the /etc/subuid or /etc/subgid file.  Mappings are set up starting with an in-container ID of 0 and then a host-level ID taken from the lowest range that matches the specified name, and using the length of that range. Additional ranges are then assigned, using the ranges which specify the lowest host-level IDs first, to the lowest not-yet-mapped in-container ID, until all of the entries have been used for maps.  This setting overrides the Remap-UIDs/GIDs setting.
  Example
     remap-user = "containers"
     remap-group = "containers"
 **root-auto-userns-user**=""
  Root-auto-userns-user is a user name which can be used to look up one or more UID/GID ranges in the /etc/subuid and /etc/subgid file.  These ranges will be partitioned to containers configured to create automatically a user namespace.  Containers configured to automatically create a user namespace can still overlap with containers having an explicit mapping set.  This setting is ignored when running as rootless.
@ -141,6 +96,34 @@ containers/storage supports three keys
 **disable-volatile**=true
  If disable-volatile is set, then the "volatile" mount optimization is disabled for all the containers.
 ### STORAGE PULL OPTIONS TABLE
 The `storage.options.pull_options` table supports the following keys:
 **enable_partial_images="true"|"false"**
  Enable the "zstd:chunked" feature, which allows partial pulls, reusing
  content that already exists on the system. This is disabled by default,
  and must be explicitly enabled to be used. For more on zstd:chunked, see
  <https://github.com/containers/storage/blob/main/docs/containers-storage-zstd-chunked.md>.
  This is a "string bool": "false"|"true" (cannot be native TOML boolean)
 **use_hard_links="false"|"true"**
  Tells containers/storage to use hard links rather then create new files in
  the image, if an identical file already existed in storage.
  This is a "string bool": "false"|"true" (cannot be native TOML boolean)
 **ostree_repos=""**
  Path to an ostree repository that might have
  previously pulled content which can be used when attempting to avoid
  pulling content from the container registry.
 **convert_images="false"|"true"**
  If set to "true", containers/storage will convert images that are
  not already in zstd:chunked format to that format before processing
  in order to take advantage of local deduplication and hard linking.
  It is an expensive operation so it is not enabled by default.
  This is a "string bool": "false"|"true" (cannot be native TOML boolean)
 ### STORAGE OPTIONS FOR AUFS TABLE
 The `storage.options.aufs` table supports the following options:
@ -158,72 +141,13 @@ The `storage.options.btrfs` table supports the following options:
 **size**=""
  Maximum size of a container image.   This flag can be used to set quota on the size of container images. (format: <number>[<unit>], where unit = b (bytes), k (kilobytes), m (megabytes), or g (gigabytes))
 ### STORAGE OPTIONS FOR THINPOOL (devicemapper) TABLE
 The `storage.options.thinpool` table supports the following options for the `devicemapper` driver:
 **autoextend_percent**=""
  Tells the thinpool driver the amount by which the thinpool needs to be grown. This is specified in terms of % of pool size. So a value of 20 means that when threshold is hit, pool will be grown by 20% of existing pool size. (default: 20%)
 **autoextend_threshold**=""
  Tells the driver the thinpool extension threshold in terms of percentage of pool size. For example, if threshold is 60, that means when pool is 60% full, threshold has been hit. (default: 80%)
 **basesize**=""
  Specifies the size to use when creating the base device, which limits the size of images and containers. (default: 10g)
 **blocksize**=""
  Specifies a custom blocksize to use for the thin pool. (default: 64k)
 **directlvm_device**=""
  Specifies a custom block storage device to use for the thin pool. Required for using graphdriver `devicemapper`.
 **directlvm_device_force**=""
  Tells driver to wipe device (directlvm_device) even if device already has a filesystem.  (default: false)
 **fs**="xfs"
  Specifies the filesystem type to use for the base device. (default: xfs)
 **log_level**=""
  Sets the log level of devicemapper.
    0: LogLevelSuppress 0 (default)
    2: LogLevelFatal
    3: LogLevelErr
    4: LogLevelWarn
    5: LogLevelNotice
    6: LogLevelInfo
    7: LogLevelDebug
 **metadata_size**=""
  metadata_size is used to set the `pvcreate --metadatasize` options when creating thin devices. (Default 128k)
 **min_free_space**=""
  Specifies the min free space percent in a thin pool required for new device creation to succeed. Valid values are from 0% - 99%. Value 0% disables. (default: 10%)
 **mkfsarg**=""
  Specifies extra mkfs arguments to be used when creating the base device.
 **mountopt**=""
  Comma separated list of default options to be used to mount container images.  Suggested value "nodev". Mount options are documented in the mount(8) man page.
 **size**=""
  Maximum size of a container image.  This flag can be used to set quota on the size of container images. (format: <number>[<unit>], where unit = b (bytes), k (kilobytes), m (megabytes), or g (gigabytes))
 **use_deferred_deletion**=""
  Marks thinpool device for deferred deletion. If the thinpool is in use when the driver attempts to delete it, the driver will attempt to delete device every 30 seconds until successful, or when it restarts.  Deferred deletion permanently deletes the device and all data stored in the device will be lost. (default: true).
 **use_deferred_removal**=""
  Marks devicemapper block device for deferred removal.  If the device is in use when its driver attempts to remove it, the driver tells the kernel to remove the device as soon as possible.  Note this does not free up the disk space, use deferred deletion to fully remove the thinpool.  (default: true).
 **xfs_nospace_max_retries**=""
  Specifies the maximum number of retries XFS should attempt to complete IO when ENOSPC (no space) error is returned by underlying storage device. (default: 0, which means to try continuously.)
 ### STORAGE OPTIONS FOR OVERLAY TABLE
 The `storage.options.overlay` table supports the following options:
 **ignore_chown_errors** = "false"
-  ignore_chown_errors can be set to allow a non privileged user running with a  single UID within a user namespace to run containers. The user can pull and use any image even those with multiple uids.  Note multiple UIDs will be squashed down to the default uid in the container.  These images will have no separation between the users in the container. (default: false)
+  ignore_chown_errors can be set to allow a non privileged user running with a  single UID within a user namespace to run containers. The user can pull and use any image even those with multiple uids.  Note multiple UIDs will be squashed down to the default uid in the container.  These images will have no separation between the users in the container. (default: "false")
  This is a "string bool": "false"|"true" (cannot be native TOML boolean)
 **inodes**=""
  Maximum inodes in a read/write layer.   This flag can be used to set a quota on the inodes allocated for a read/write layer of a container.
@ -272,18 +196,26 @@ based file systems.
 **mountopt**=""
  Comma separated list of default options to be used to mount container images.  Suggested value "nodev". Mount options are documented in the mount(8) man page.
-**skip_mount_home=""**
+**skip_mount_home="false"**
  Tell storage drivers to not create a PRIVATE bind mount on their home directory.
  This is a "string bool": "false"|"true" (cannot be native TOML boolean)
 **size**=""
  Maximum size of a read/write layer.   This flag can be used to set quota on the size of a read/write layer of a container. (format: <number>[<unit>], where unit = b (bytes), k (kilobytes), m (megabytes), or g (gigabytes))
 **use_composefs** = "false"
    Use ComposeFS to mount the data layers image.  ComposeFS support is experimental and not recommended for production use.
    This is a "string bool": "false"|"true" (cannot be native TOML boolean)
 ### STORAGE OPTIONS FOR VFS TABLE
 The `storage.options.vfs` table supports the following options:
 **ignore_chown_errors** = "false"
-  ignore_chown_errors can be set to allow a non privileged user running with a  single UID within a user namespace to run containers. The user can pull and use any image even those with multiple uids.  Note multiple UIDs will be squashed down to the default uid in the container.  These images will have no separation between the users in the container. (default: false)
+  ignore_chown_errors can be set to allow a non privileged user running with a  single UID within a user namespace to run containers. The user can pull and use any image even those with multiple uids.  Note multiple UIDs will be squashed down to the default uid in the container.  These images will have no separation between the users in the container.
  This is a "string bool": "false"|"true" (cannot be native TOML boolean)
 ### STORAGE OPTIONS FOR ZFS TABLE
--- a/SOURCES/containers-transports.5.md
+++ b/SOURCES/containers-transports.5.md
@ -9,7 +9,7 @@ containers-transports - description of supported transports for copying and stor
 ## DESCRIPTION
 Tools which use the containers/image library, including skopeo(1), buildah(1), podman(1), all share a common syntax for referring to container images in various locations.
-The general form of the syntax is _transport:details_, where details are dependent on the specified transport, which are documented below.
+The general form of the syntax is _transport_`:`_details_, where details are dependent on the specified transport, which are documented below.
 The semantics of the image names ultimately depend on the environment where
 they are evaluated. For example: if evaluated on a remote server, image names
@ -18,14 +18,14 @@ directory of the image consumer.
 <!-- atomic: is deprecated and not documented here. -->
-### **containers-storage**:[**[**storage-specifier**]**]{image-id|docker-reference[@image-id]}
+### **containers-storage:**[**[**_storage-specifier_**]**]{_image-id_|_docker-reference_[**@**_image-id_]}
 An image located in a local containers storage.
 The format of _docker-reference_ is described in detail in the **docker** transport.
-The _storage-specifier_ allows for referencing storage locations on the file system and has the format `[[driver@]root[+run-root][:options]]` where the optional `driver` refers to the storage driver (e.g., overlay or btrfs) and where `root` is an absolute path to the storage's root directory.
+The _storage-specifier_ allows for referencing storage locations on the file system and has the format `[`[_driver_`@`]_root_[`+`_run-root_][`:`_options_]`]` where the optional _driver_ refers to the storage driver (e.g., `overlay` or `btrfs`) and where _root_ is an absolute path to the storage's root directory.
-The optional `run-root` can be used to specify the run directory of the storage where all temporary writable content is stored.
+The optional _run-root_ can be used to specify the run directory of the storage where all temporary writable content is stored.
-The optional `options` are a comma-separated list of driver-specific options.
+The optional _options_ are a comma-separated list of driver-specific options.
 Please refer to containers-storage.conf(5) for further information on the drivers and supported options.
 ### **dir:**_path_
@ -40,34 +40,38 @@ By default, uses the authorization state in `$XDG_RUNTIME_DIR/containers/auth.js
 If the authorization state is not found there, `$HOME/.docker/config.json` is checked, which is set using docker-login(1).
 The containers-registries.conf(5) further allows for configuring various settings of a registry.
-Note that a _docker-reference_ has the following format: _name_[**:**_tag_ | **@**_digest_].
+Note that a _docker-reference_ has the following format: _name_[`:`_tag_ | `@`_digest_].
 While the docker transport does not support both a tag and a digest at the same time some formats like containers-storage do.
 Digests can also be used in an image destination as long as the manifest matches the provided digest.
-The docker transport supports pushing images without a tag or digest to a registry when the image name is suffixed with **@@unknown-digest@@**. The _name_**@@unknown-digest@@** reference format cannot be used with a reference that has a tag or digest.
+The docker transport supports pushing images without a tag or digest to a registry when the image name is suffixed with `@@unknown-digest@@`. The _name_`@@unknown-digest@@` reference format cannot be used with a reference that has a tag or digest.
 The digest of images can be explored with skopeo-inspect(1).
-If `name` does not contain a slash, it is treated as `docker.io/library/name`.
+If _name_ does not contain a slash, it is treated as `docker.io/library/`_name_.
-Otherwise, the component before the first slash is checked if it is recognized as a `hostname[:port]` (i.e., it contains either a . or a :, or the component is exactly localhost).
+Otherwise, the component before the first slash is checked if it is recognized as a _hostname_[`:`_port_] (i.e., it contains either a `.` or a `:`, or the component is exactly `localhost`).
-If the first component of name is not recognized as a `hostname[:port]`, `name` is treated as `docker.io/name`.
+If the first component of name is not recognized as a _hostname_[`:`_port_], _name_ is treated as `docker.io/`_name_.
-### **docker-archive:**_path[:{docker-reference|@source-index}]_
+### **docker-archive:**_path_[`:`{_docker-reference_|`@`_source-index_}]
 An image is stored in the docker-save(1) formatted file.
-_docker-reference_ must not contain a digest.
+
-Alternatively, for reading archives, @_source-index_ is a zero-based index in archive manifest
+Unless a tool explicitly documents otherwise,
-(to access untagged images).
+a write to a **docker-archive:** destination completely overwrites _path_, replacing it with the single provided image.
 If neither _docker-reference_ nor @_source_index is specified when reading an archive, the archive must contain exactly one image.
 The _path_ can refer to a stream, e.g. `docker-archive:/dev/stdin`.
-### **docker-daemon:**_docker-reference|algo:digest_
+_docker-reference_ must not contain a digest.
 Alternatively, for reading archives, `@`_source-index_ is a zero-based index in archive manifest
 (to access untagged images).
 If neither _docker-reference_ nor `@`_source_index is specified when reading an archive, the archive must contain exactly one image.
 ### **docker-daemon:**_docker-reference_|_algo_`:`_digest_
 An image stored in the docker daemon's internal storage.
-The image must be specified as a _docker-reference_ or in an alternative _algo:digest_ format when being used as an image source.
+The image must be specified as a _docker-reference_ or in an alternative _algo_`:`_digest_ format when being used as an image source.
-The _algo:digest_ refers to the image ID reported by docker-inspect(1).
+The _algo_`:`_digest_ refers to the image ID reported by docker-inspect(1).
-### **oci:**_path[:reference]_
+### **oci:**_path_[`:`_reference_]
 An image in a directory structure compliant with the "Open Container Image Layout Specification" at _path_.
@ -75,18 +79,21 @@ The _path_ value terminates at the first `:` character; any further `:` characte
 The _reference_ is used to set, or match, the `org.opencontainers.image.ref.name` annotation in the top-level index.
 If _reference_ is not specified when reading an image, the directory must contain exactly one image.
-### **oci-archive:**_path[:reference]_
+### **oci-archive:**_path_[`:`_reference_]
 An image in a tar(1) archive with contents compliant with the "Open Container Image Layout Specification" at _path_.
 Unless a tool explicitly documents otherwise,
 a write to an **oci-archive:** destination completely overwrites _path_, replacing it with the single provided image.
 The _path_ value terminates at the first `:` character; any further `:` characters are not separators, but a part of _reference_.
 The _reference_ is used to set, or match, the `org.opencontainers.image.ref.name` annotation in the top-level index.
 If _reference_ is not specified when reading an archive, the archive must contain exactly one image.
-### **ostree:**_docker-reference[@/absolute/repo/path]_
+### **ostree:**_docker-reference_[`@`_/absolute/repo/path_]
 An image in the local ostree(1) repository.
-_/absolute/repo/path_ defaults to _/ostree/repo_.
+_/absolute/repo/path_ defaults to `/ostree/repo`.
 ### **sif:**_path_
--- a/SOURCES/containers.conf
+++ b/SOURCES/containers.conf
@ -10,7 +10,8 @@
 # locations in the following order:
 #  1. /usr/share/containers/containers.conf
 #  2. /etc/containers/containers.conf
-#  3. $HOME/.config/containers/containers.conf (Rootless containers ONLY)
+#  3. $XDG_CONFIG_HOME/containers/containers.conf or
 #     $HOME/.config/containers/containers.conf if $XDG_CONFIG_HOME is not set
 #  Items specified in the latter containers.conf, if they exist, override the
 # previous containers.conf settings, or the default settings.
@ -26,16 +27,19 @@
 #
 #apparmor_profile = "container-default"
-# The hosts entries from the base hosts file are added to the containers hosts
+# Base file to create the `/etc/hosts` file inside the container. This must either
-# file. This must be either an absolute path or as special values "image" which
+# be an absolute path to a file on the host system, or one of the following
-# uses the hosts file from the container image or "none" which means
+# special flags:
-# no base hosts file is used. The default is "" which will use /etc/hosts.
+# ""      Use the host's `/etc/hosts` file (the default)
 # `none`  Do not use a base file (i.e. start with an empty file)
 # `image` Use the container image's `/etc/hosts` file as base file
 #
 #base_hosts_file = ""
 # List of cgroup_conf entries specifying a list of cgroup files to write to and
 # their values. For example `memory.high=1073741824` sets the
 # memory.high limit to 1GB.
 #
 # cgroup_conf = []
 # Default way to to create a cgroup namespace for the container
@ -57,20 +61,19 @@
 # List of default capabilities for containers. If it is empty or commented out,
 # the default capabilities defined in the container engine will be added.
 #
-default_capabilities = [
+#default_capabilities = [
-  "NET_RAW",
+#  "CHOWN",
-  "CHOWN",
+#  "DAC_OVERRIDE",
-  "DAC_OVERRIDE",
+#  "FOWNER",
-  "FOWNER",
+#  "FSETID",
-  "FSETID",
+#  "KILL",
-  "KILL",
+#  "NET_BIND_SERVICE",
-  "NET_BIND_SERVICE",
+#  "SETFCAP",
-  "SETFCAP",
+#  "SETGID",
-  "SETGID",
+#  "SETPCAP",
-  "SETPCAP",
+#  "SETUID",
-  "SETUID",
+#  "SYS_CHROOT",
-  "SYS_CHROOT",
+#]
 ]
 # A list of sysctls to be set in containers by default,
 # specified as "name=value",
@ -126,13 +129,25 @@ default_sysctls = [
 #
 #env_host = false
-# Set the ip for the host.containers.internal entry in the containers /etc/hosts
+# Set the IP address the container should expect to connect to the host. The IP
-# file. This can be set to "none" to disable adding this entry. By default it
+# address is used by Podman to automatically add the `host.containers.internal`
-# will automatically choose the host ip.
+# and `host.docker.internal` hostnames to the container's `/etc/hosts` file. It
 # is also used for the *host-gateway* flag of Podman's `--add-host` CLI option.
 # If no IP address is configured (the default), Podman will try to determine it
 # automatically, but might fail to do so depending on the container's network
 # setup. Adding these internal hostnames to `/etc/hosts` is silently skipped then.
 # Set this config to `none` to never add the internal hostnames to `/etc/hosts`.
 #
-# NOTE: When using podman machine this entry will never be added to the containers
+# Note: If Podman is running in a virtual machine using `podman machine` (this
-# hosts file instead the gvproxy dns resolver will resolve this hostname. Therefore
+# includes Mac and Windows hosts), Podman will silently skip adding the internal
-# it is not possible to disable the entry in this case.
+# hostnames to `/etc/hosts`, unless an IP address was configured manually. The
 # internal hostnames are resolved by the gvproxy DNS resolver instead. This config
 # has no effect on gvproxy. However, since `/etc/hosts` bypasses the DNS resolver,
 # a manually configured IP address still takes precedence.
 #
 # Note: This config doesn't affect the actual network setup, it just tells Podman
 # the IP address it should expect. Configuring an IP address here doesn't ensure
 # that the container can actually reach the host using this IP address.
 #
 #host_containers_internal_ip = ""
@ -165,6 +180,13 @@ default_sysctls = [
 #
 #ipcns = "shareable"
 # Default way to set an interface name inside container. Defaults to legacy
 # pattern of ethX, where X is a integer, when left undefined.
 # Options are:
 #  "device"   Uses the network_interface name from the network config as interface name.
 #             Falls back to the ethX pattern if the network_interface is not set.
 #interface_name = ""
 # keyring tells the container engine whether to create
 # a kernel keyring for use within the container.
 #
@ -215,8 +237,10 @@ log_driver = "k8s-file"
 #
 #netns = "private"
-# Create /etc/hosts for the container.  By default, container engine manage
+# Do not modify the `/etc/hosts` file in the container. Podman assumes control
-# /etc/hosts, automatically adding  the container's  own  IP  address.
+# over the container's `/etc/hosts` file by default; refer to the `--add-host`
 # CLI option for details. To disable this, either set this config to `true`, or
 # use the functionally identical `--no-hosts` CLI option.
 #
 #no_hosts = false
@ -322,7 +346,6 @@ log_driver = "k8s-file"
 # iptables rules and network interfaces might leak on the host. A reboot will fix this.
 #
 #network_backend = ""
 network_backend = "cni"
 # Path to directory where CNI plugin binaries are located.
 #
@ -343,6 +366,14 @@ network_backend = "cni"
 #  "/usr/lib/netavark",
 #]
 # The firewall driver to be used by netavark.
 # The default is empty which means netavark will pick one accordingly. Current supported
 # drivers are "iptables", "nftables", "none" (no firewall rules will be created) and "firewalld" (firewalld is
 # experimental at the moment and not recommend outside of testing).
 #
 #firewall_driver = ""
 # The network name of the default network to attach pods to.
 #
 #default_network = "podman"
@ -371,9 +402,9 @@ network_backend = "cni"
 # Configure which rootless network program to use by default. Valid options are
-# `slirp4netns` (default) and `pasta`.
+# `slirp4netns` and `pasta` (default).
 #
-#default_rootless_network_cmd = "slirp4netns"
+#default_rootless_network_cmd = "pasta"
 # Path to the directory where network configuration files are located.
 # For the CNI backend the default is "/etc/cni/net.d" as root
@ -403,6 +434,8 @@ network_backend = "cni"
 #List of compression algorithms. If set makes sure that requested compression variant
 #for each platform is added to the manifest list keeping original instance intact in
 #the same manifest list on every `manifest push`. Supported values are (`gzip`, `zstd` and `zstd:chunked`).
 #`zstd:chunked` is incompatible with encrypting images, and will be treated as `zstd` with a warning
 #in that case.
 #
 #add_compression = ["gzip", "zstd", "zstd:chunked"]
@ -422,6 +455,11 @@ network_backend = "cni"
 # The compression format to use when pushing an image.
 # Valid options are: `gzip`, `zstd` and `zstd:chunked`.
 # This field is ignored when pushing images to the docker-daemon and
 # docker-archive formats. It is also ignored when the manifest format is set
 # to v2s2.
 # `zstd:chunked` is incompatible with encrypting images, and will be treated as `zstd` with a warning
 # in that case.
 #
 #compression_format = "gzip"
@ -508,12 +546,20 @@ network_backend = "cni"
 # Valid values are `journald`, `file` and `none`.
 #
 #events_logger = "journald"
 events_logger = "file"
 # Creates a more verbose container-create event which includes a JSON payload
 # with detailed information about the container.
 #events_container_create_inspect_data = false
 # Whenever Podman should log healthcheck events.
 # With many running healthcheck on short interval Podman will spam the event
 # log a lot as it generates a event for each single healthcheck run. Because
 # this event is optional and only useful to external consumers that may want
 # to know when a healthcheck is run or failed allow users to turn it off by
 # setting it to false. The default is true.
 #
 #healthcheck_events = true
 # A is a list of directories which are used to search for helper binaries.
 #
 #helper_binaries_dir = [
@ -529,6 +575,12 @@ events_logger = "file"
 #  "/usr/share/containers/oci/hooks.d",
 #]
 # Directories to scan for CDI Spec files.
 #
 #cdi_spec_dirs = [
 #  "/etc/cdi",
 #]
 # Manifest Type (oci, v2s2, or v2s1) to use when pulling, pushing, building
 # container images. By default image pulled and pushed match the format of the
 # source image. Building/committing defaults to OCI.
@ -545,7 +597,7 @@ events_logger = "file"
 #image_parallel_copies = 0
 # Tells container engines how to handle the built-in image volumes.
-#   * bind: An anonymous named volume will be created and mounted
+#   * anonymous: An anonymous named volume will be created and mounted
 #     into the container.
 #   * tmpfs: The volume is mounted onto the container as a tmpfs,
 #     which allows users to create content that disappears when
@ -624,7 +676,8 @@ events_logger = "file"
 #
 #no_pivot_root = false
-# Number of locks available for containers and pods.
+# Number of locks available for containers, pods, and volumes. Each container,
 # pod, and volume consumes 1 lock for as long as it exists.
 # If this is changed, a lock renumber must be performed (e.g. with the
 # 'podman system renumber' command).
 #
@ -643,10 +696,20 @@ events_logger = "file"
 #
 #remote = false
 # Number of times to retry pulling/pushing images in case of failure
 #
 #retry = 3
 # Delay between retries in case pulling/pushing image fails.
 # If set, container engines will retry at the set interval,
 # otherwise they delay 2 seconds and then exponentially back off.
 #
 #retry_delay = "2s"
 # Default OCI runtime
 #
 #runtime = "crun"
-runtime = "runc"
+runtime = "crun"
 # List of the OCI runtimes that support --format=json. When json is supported
 # engine will use it for reporting nicer errors.
@ -719,9 +782,6 @@ runtime = "runc"
 # A value of 0 is treated as no timeout.
 #volume_plugin_timeout = 5
 # Default timeout in seconds for podmansh logins.
 #podmansh_timeout = 30
 # Paths to look for a valid OCI runtime (crun, runc, kata, runsc, krun, etc)
 [engine.runtimes]
 #crun = [
@ -734,6 +794,15 @@ runtime = "runc"
 #  "/run/current-system/sw/bin/crun",
 #]
 #crun-vm = [
 #  "/usr/bin/crun-vm",
 #  "/usr/local/bin/crun-vm",
 #  "/usr/local/sbin/crun-vm",
 #  "/sbin/crun-vm",
 #  "/bin/crun-vm",
 #  "/run/current-system/sw/bin/crun-vm",
 #]
 #kata = [
 #  "/usr/bin/kata-runtime",
 #  "/usr/sbin/kata-runtime",
@ -789,16 +858,15 @@ runtime = "runc"
 #
 #disk_size=10
-# Default image URI when creating a new VM using `podman machine init`.
+# Default Image used when creating a new VM using `podman machine init`.
-# Options: On Linux/Mac, `testing`, `stable`, `next`. On Windows, the major
+# Can be specified as registry with a bootable OCI artifact, download URL, or a local path.
-# version of the OS (e.g `36`) for Fedora 36. For all platforms you can
+# Registry target must be in the form of `docker://registry/repo/image:version`.
-# alternatively specify a custom download URL to an image. Container engines
+# Container engines translate URIs $OS and $ARCH to the native OS and ARCH.
-# translate URIs $OS and $ARCH to the native OS and ARCH. URI
+# URI "https://example.com/$OS/$ARCH/foobar.ami" would become
 # "https://example.com/$OS/$ARCH/foobar.ami" becomes
 # "https://example.com/linux/amd64/foobar.ami" on a Linux AMD machine.
-# The default value is `testing`.
+# If unspecified, the default Podman machine image will be used.
 #
-#image = "testing"
+#image = ""
 # Memory in MB a machine is created with.
 #
@ -820,9 +888,22 @@ runtime = "runc"
 # Virtualization provider used to run Podman machine.
 # If it is empty or commented out, the default provider will be used.
-#
+# Linux:
 #    qemu    - Open source machine emulator and virtualizer. (Default)
 # Windows: there are currently two options:
 #    wsl     - Windows Subsystem for Linux (Default) 
 #    hyperv  - Windows Server Virtualization
 # Mac: there are currently two options:
 #    applehv - Default Apple Hypervisor (Default)
 #    libkrun - Launch virtual machines using the libkrun platform, optimized
 #              for sharing GPU with the machine.
 #provider = ""
 # Rosetta supports running x86_64 Linux binaries on a Podman machine on Apple silicon.
 # The default value is `true`. Supported on AppleHV(arm64) machines only.
 #
 #rosetta=true
 # The [machine] table MUST be the last entry in this file.
 # (Unless another table is added)
 # TOML does not provide a way to end a table other than a further table being
@ -836,3 +917,14 @@ runtime = "runc"
 #
 # map of existing farms
 #[farms.list]
 [podmansh]
 # Shell to spawn in container. Default: /bin/sh.
 #shell = "/bin/sh"
 #
 # Name of the container the podmansh user should join.
 #container = "podmansh"
 #
 # Default timeout in seconds for podmansh logins.
 # Favored over the deprecated "podmansh_timeout" field.
 #timeout = 30
--- a/SOURCES/containers.conf.5.md
+++ b/SOURCES/containers.conf.5.md
@ -11,10 +11,9 @@ a TOML format that can be easily modified and versioned.
 Container engines read the __/usr/share/containers/containers.conf__,
 __/etc/containers/containers.conf__, and __/etc/containers/containers.conf.d/\*.conf__
-files if they exist.
+for global configuration that effects all users.
-When running in rootless mode, they also read
+For user specific configuration it reads __\$XDG_CONFIG_HOME/containers/containers.conf__ and
-__$HOME/.config/containers/containers.conf__ and
+__\$XDG_CONFIG_HOME/containers/containers.conf.d/\*.conf__ files. When `$XDG_CONFIG_HOME` is not set it falls back to using `$HOME/.config` instead.
 __$HOME/.config/containers/containers.conf.d/\*.conf__ files.
 Fields specified in containers conf override the default options, as well as
 options in previously read containers.conf files.
@ -42,13 +41,13 @@ instance, `CONTAINERS_CONF=/tmp/my_containers.conf`.
 ## MODULES
 A module is a containers.conf file located directly in or a sub-directory of the following three directories:
- - __$HOME/.config/containers/containers.conf.modules__
+ - __\$XDG_CONFIG_HOME/containers/containers.conf.modules__ or  __\$HOME/.config/containers/containers.conf.modules__ if `$XDG_CONFIG_HOME` is not set.
 - __/etc/containers/containers.conf.modules__
 - __/usr/share/containers/containers.conf.modules__
 Files in those locations are not loaded by default but only on-demand.  They are loaded after all system and user configuration files but before `CONTAINERS_CONF_OVERRIDE` hence allowing for overriding system and user configs.
-Modules are currently supported by podman(1).  The `podman --module` flag allows for loading a module and can be specified multiple times.  If the specified value is an absolute path, the config file will be loaded directly.  Relative paths are resolved relative to the three module directories mentioned above and in the specified order such that modules in `$HOME` allow for overriding those in `/etc` and `/usr/share`.  Modules in `$HOME` (or `$XDG_CONFIG_HOME` if specified) are only used for rootless users.
+Modules are currently supported by podman(1).  The `podman --module` flag allows for loading a module and can be specified multiple times.  If the specified value is an absolute path, the config file will be loaded directly.  Relative paths are resolved relative to the three module directories mentioned above and in the specified order such that modules in `$XDG_CONFIG_HOME/$HOME` allow for overriding those in `/etc` and `/usr/share`.
 ## APPENDING TO STRING ARRAYS
@ -59,7 +58,7 @@ Consider the following example:
 modules1.conf: env=["1=true"]
 modules2.conf: env=["2=true"]
 modules3.conf: env=["3=true", {append=true}]
-modules3.conf: env=["4=true"]
+modules4.conf: env=["4=true"]
 ```
 After loading the files in the given order, the final contents are `env=["2=true", "3=true", "4=true"]`.  If modules4.conf would set `{append=false}`, the final contents would be `env=["4=true"]`.
@ -97,10 +96,12 @@ The default profile name is "container-default".
 **base_hosts_file**=""
-The hosts entries from the base hosts file are added to the containers hosts
+Base file to create the `/etc/hosts` file inside the container. This must either
-file. This must be either an absolute path or as special values "image" which
+be an absolute path to a file on the host system, or one of the following
-uses the hosts file from the container image or "none" which means
+special flags:
-no base hosts file is used. The default is "" which will use /etc/hosts.
+  ""      Use the host's `/etc/hosts` file (the default)
  `none`  Do not use a base file (i.e. start with an empty file)
  `image` Use the container image's `/etc/hosts` file as base file
 **cgroup_conf**=[]
@ -118,7 +119,7 @@ Options are:
 **cgroupns**="private"
-Default way to to create a cgroup namespace for the container.
+Default way to create a cgroup namespace for the container.
 Options are:
 `private` Create private Cgroup Namespace for the container.
 `host`    Share host Cgroup Namespace with the container.
@ -196,13 +197,25 @@ Pass all host environment variables into the container.
 **host_containers_internal_ip**=""
-Set the ip for the host.containers.internal entry in the containers /etc/hosts
+Set the IP address the container should expect to connect to the host. The IP
-file. This can be set to "none" to disable adding this entry. By default it
+address is used by Podman to automatically add the `host.containers.internal`
-will automatically choose the host ip.
+and `host.docker.internal` hostnames to the container's `/etc/hosts` file. It
 is also used for the *host-gateway* flag of Podman's `--add-host` CLI option.
 If no IP address is configured (the default), Podman will try to determine it
 automatically, but might fail to do so depending on the container's network
 setup. Adding these internal hostnames to `/etc/hosts` is silently skipped then.
 Set this config to `none` to never add the internal hostnames to `/etc/hosts`.
-NOTE: When using podman machine this entry will never be added to the containers
+Note: If Podman is running in a virtual machine using `podman machine` (this
-hosts file instead the gvproxy dns resolver will resolve this hostname. Therefore
+includes Mac and Windows hosts), Podman will silently skip adding the internal
-it is not possible to disable the entry in this case.
+hostnames to `/etc/hosts`, unless an IP address was configured manually. The
 internal hostnames are resolved by the gvproxy DNS resolver instead. This config
 has no effect on gvproxy. However, since `/etc/hosts` bypasses the DNS resolver,
 a manually configured IP address still takes precedence.
 Note: This config doesn't affect the actual network setup, it just tells Podman
 the IP address it should expect. Configuring an IP address here doesn't ensure
 that the container can actually reach the host using this IP address.
 **http_proxy**=true
@ -227,9 +240,16 @@ Path to the container-init binary, which forwards signals and reaps processes
 within containers. Note that the container-init binary will only be used when
 the `--init` for podman-create and podman-run is set.
 **interface_name**=""
 Default way to set interface names inside containers. Defaults to legacy pattern
 of ethX, where X is an integer, when left undefined.
 Options are:
  `device`   Uses the network_interface name from the network config as interface name. Falls back to the ethX pattern if the network_interface is not set.
 **ipcns**="shareable"
-Default way to to create a IPC namespace for the container.
+Default way to create a IPC namespace for the container.
 Options are:
  `host`     Share host IPC Namespace with the container.
  `none`     Create shareable IPC Namespace for the container without a private /dev/shm.
@ -276,7 +296,7 @@ Example:  [ "type=bind,source=/var/lib/foobar,destination=/var/lib/foobar,ro", ]
 **netns**="private"
-Default way to to create a NET namespace for the container.
+Default way to create a NET namespace for the container.
 Options are:
  `private` Create private NET Namespace for the container.
  `host`    Share host NET Namespace with the container.
@ -284,8 +304,10 @@ Options are:
 **no_hosts**=false
-Create /etc/hosts for the container. By default, container engines manage
+Do not modify the `/etc/hosts` file in the container. Podman assumes control
-/etc/hosts, automatically adding  the container's  own  IP  address.
+over the container's `/etc/hosts` file by default; refer to the `--add-host`
 CLI option for details. To disable this, either set this config to `true`, or
 use the functionally identical `--no-hosts` CLI option.
 **oom_score_adj**=0
@ -293,7 +315,7 @@ Tune the host's OOM preferences for containers (accepts values from -1000 to 100
 **pidns**="private"
-Default way to to create a PID namespace for the container.
+Default way to create a PID namespace for the container.
 Options are:
  `private` Create private PID Namespace for the container.
  `host`    Share host PID Namespace with the container.
@ -346,14 +368,14 @@ Sets umask inside the container.
 **userns**="host"
-Default way to to create a USER namespace for the container.
+Default way to create a USER namespace for the container.
 Options are:
  `private` Create private USER Namespace for the container.
  `host`    Share host USER Namespace with the container.
 **utsns**="private"
-Default way to to create a UTS namespace for the container.
+Default way to create a UTS namespace for the container.
 Options are:
  `private` Create private UTS Namespace for the container.
  `host`    Share host UTS Namespace with the container.
@ -436,10 +458,10 @@ default_subnet_pools = [
 ]
 ```
-**default_rootless_network_cmd**="slirp4netns"
+**default_rootless_network_cmd**="pasta"
 Configure which rootless network program to use by default. Valid options are
-`slirp4netns` (default) and `pasta`.
+`slirp4netns` and `pasta` (default).
 **network_config_dir**="/etc/cni/net.d/"
@ -449,6 +471,13 @@ and __$HOME/.config/cni/net.d__ as rootless.
 For the netavark backend "/etc/containers/networks" is used as root
 and "$graphroot/networks" as rootless.
 **firewall_driver**=""
 The firewall driver to be used by netavark.
 The default is empty which means netavark will pick one accordingly. Current supported
 drivers are "iptables", "nftables", "none" (no firewall rules will be created) and "firewalld" (firewalld is
 experimental at the moment and not recommend outside of testing).
 **dns_bind_port**=53
 Port to use for dns forwarding daemon with netavark in rootful bridge
@ -473,6 +502,9 @@ Name of destination for accessing the Podman service. See SERVICE DESTINATION TA
 List of compression algorithms. If set makes sure that requested compression variant
 for each platform is added to the manifest list keeping original instance intact in
 the same manifest list on every `manifest push`. Supported values are (`gzip`, `zstd` and `zstd:chunked`).
 `zstd:chunked` is incompatible with encrypting images, and will be treated as `zstd` with a warning
 in that case.
 Note: This is different from `compression_format` which allows users to select a default
 compression format for `push` and `manifest push`, while `add_compression` is limited to
@ -569,7 +601,7 @@ The unit can be b (bytes), k (kilobytes), m (megabytes) or g (gigabytes).
 The format for the size is `<number><unit>`, e.g., `1b` or `3g`.
 If no unit is included then the size will be in bytes.
 When the limit is exceeded, the logfile will be rotated and the old one will be deleted.
-If the maximumn size is set to 0, then no limit will be applied,
+If the maximum size is set to 0, then no limit will be applied,
 and the logfile will not be rotated.
 **events_logger**="journald"
@ -580,7 +612,7 @@ The default method is different based on the platform that
 Podman is being run upon.  To determine the current value,
 use this command:
-`podman info --format {{.Host.EventLogger}`
+`podman info --format {{.Host.EventLogger}}`
 Valid values are: `file`, `journald`, and `none`.
@ -589,6 +621,17 @@ Valid values are: `file`, `journald`, and `none`.
 Creates a more verbose container-create event which includes a JSON payload
 with detailed information about the container.  Set to false by default.
 **healthcheck_events**=true|false
 Whenever Podman should log healthcheck events.
 With many running healthcheck on short interval Podman will spam the event
 log a lot as it generates a event for each single healthcheck run. Because
 this event is optional and only useful to external consumers that may want
 to know when a healthcheck is run or failed allow users to turn it off by
 setting it to false.
 Default is true.
 **helper_binaries_dir**=["/usr/libexec/podman", ...]
 A is a list of directories which are used to search for helper binaries.
@ -630,6 +673,10 @@ The default path on Windows is:
 Path to the OCI hooks directories for automatically executed hooks.
 **cdi_spec_dirs**=["/etc/cdi", ...]
 Directories to scan for CDI Spec files.
 **image_default_format**="oci"|"v2s2"|"v2s1"
 Manifest Type (oci, v2s2, or v2s1) to use when pulling, pushing, building
@ -722,10 +769,11 @@ Whether to use chroot instead of pivot_root in the runtime.
 **num_locks**=2048
-Number of locks available for containers and pods. Each created container or
+Number of locks available for containers, pods, and volumes.
-pod consumes one lock. The default number available is 2048. If this is
+Each created container, pod, or volume consumes one lock.
-changed, a lock renumbering must be performed, using the
+Locks are recycled and can be reused after the associated container, pod, or volume is removed.
-`podman system renumber` command.
+The default number available is 2048.
 If this is changed, a lock renumbering must be performed, using the `podman system renumber` command.
 **pod_exit_policy**="continue"
@ -749,13 +797,21 @@ Pull image before running or creating a container. The default is **missing**.
 Indicates whether the application should be running in remote mode. This flag modifies the
 --remote option on container engines. Setting the flag to true will default `podman --remote=true` for access to the remote Podman service.
 **retry** = 3
 Number of times to retry pulling/pushing images in case of failure.
 **retry_delay** = ""
 Delay between retries in case pulling/pushing image fails. If set, container engines will retry at the set interval, otherwise they delay 2 seconds and then exponentially back off.
 **runtime**=""
 Default OCI specific runtime in runtimes that will be used by default. Must
 refer to a member of the runtimes table. Default runtime will be searched for
-on the system using the priority: "crun", "runc", "kata".
+on the system using the priority: "crun", "runc", "runj", "kata", "runsc", "ocijail"
-**runtime_supports_json**=["crun", "runc", "kata", "runsc", "youki", "krun"]
+**runtime_supports_json**=["crun", "crun-vm", "runc", "kata", "runsc", "youki", "krun"]
 The list of the OCI runtimes that support `--format=json`.
@ -763,7 +819,7 @@ The list of the OCI runtimes that support `--format=json`.
 The list of OCI runtimes that support running containers with KVM separation.
-**runtime_supports_nocgroups**=["crun", "krun"]
+**runtime_supports_nocgroups**=["crun", "crun-vm", "krun"]
 The list of OCI runtimes that support running containers without CGroups.
@ -814,7 +870,12 @@ the primary uid/gid of the container.
 **compression_format**="gzip"
-Specifies the compression format to use when pushing an image. Supported values are: `gzip`, `zstd` and `zstd:chunked`.
+Specifies the compression format to use when pushing an image. Supported values
 are: `gzip`, `zstd` and `zstd:chunked`. This field is ignored when pushing
 images to the docker-daemon and docker-archive formats. It is also ignored
 when the manifest format is set to v2s2.
 `zstd:chunked` is incompatible with encrypting images, and will be treated as `zstd` with a warning
 in that case.
 **compression_level**="5"
@ -823,10 +884,6 @@ depend on the compression format used. For gzip, valid options are
 1-9, with a default of 5. For zstd, valid options are 1-20, with a
 default of 3.
 **podmansh_timeout**=30
 Number of seconds to wait for podmansh logins.
 ## SERVICE DESTINATION TABLE
 The `engine.service_destinations` table contains configuration options used to set up remote connections to the podman service for the podman API.
@ -883,13 +940,13 @@ The size of the disk in GB created when init-ing a podman-machine VM
 **image**=""
-Default image URI when creating a new VM using `podman machine init`.
+Image used when creating a new VM using `podman machine init`.
-Options: On Linux/Mac, `testing`, `stable`, `next`. On Windows, the major
+Can be specified as a registry with a bootable OCI artifact, download URL, or a local path.
-version of the OS (e.g `36`) for Fedora 36. For all platforms you can
+Registry target must be in the form of `docker://registry/repo/image:version`.
-alternatively specify a custom download URL to an image. Container engines
+Container engines translate URIs $OS and $ARCH to the native OS and ARCH.
-translate URIs $OS and $ARCH to the native OS and ARCH. URI "https://example.com/$OS/$ARCH/foobar.ami" would become "https://example.com/linux/amd64/foobar.ami" on a Linux AMD machine.
+URI "https://example.com/$OS/$ARCH/foobar.ami" would become
-The default value
+"https://example.com/linux/amd64/foobar.ami" on a Linux AMD machine.
-is `testing` on Linux/Mac, and on Windows.
+If unspecified, the default Podman machine image will be used.
 **memory**=2048
@ -914,8 +971,19 @@ On Mac, the default volumes are:
 **provider**=""
 Virtualization provider to be used for running a podman-machine VM. Empty value
-is interpreted as the default provider for the current host OS. On Linux/Mac
+is interpreted as the default provider for the current host OS.
-default is `QEMU` and on Windows it is `WSL`.
+
 | Platform | Default Virtualization provider         | Optional |
 | -------- | --------------------------------------- | -------- |
 | Linux    | "" (qemu)                               | None     |
 | Windows  | "" ("wsl": Windows Subsystem for Linux) | "hyperv" (Windows Server Virtualization) |
 | Mac      | "" ("applehv": Apple Hypervisor)        | "libkrun" (Launch machine via libkrun platform, optimized for sharing GPU with the machine) |
 **rosetta**="true"
 Rosetta supports running x86_64 Linux binaries on a Podman machine on Apple silicon.
 The default value is `true`. Supported on AppleHV(arm64) machines only.
 ## FARMS TABLE
 The `farms` table contains configuration options used to group up remote connections into farms that will be used when sending out builds to different machines in a farm via `podman buildfarm`.
@ -928,6 +996,25 @@ The default farm to use when farming out builds.
 Map of farms created where the key is the farm name and the value is the list of system connections.
 ## PODMANSH TABLE
 The `podmansh` table contains configuration options used by podmansh.
 **shell**="/bin/sh"
 The shell to spawn in the container.
 The default value is `/bin/sh`.
 **container**="podmansh"
 Name of the container that podmansh joins.
 The default value is `podmansh`.
 **timeout**=0
 Number of seconds to wait for podmansh logins. This value if favoured over the deprecated field `engine.podmansh_timeout` if set.
 The default value is 30.
 # FILES
 **containers.conf**
@ -937,8 +1024,8 @@ provide a default configuration. Administrators can override fields in this
 file by creating __/etc/containers/containers.conf__ to specify their own
 configuration. They may also drop `.conf` files in
 __/etc/containers/containers.conf.d__ which will be loaded in alphanumeric order.
-Rootless users can further override fields in the config by creating a config
+For user specific configuration it reads __\$XDG_CONFIG_HOME/containers/containers.conf__ and
-file stored in the __$HOME/.config/containers/containers.conf__ file or __.conf__ files in __$HOME/.config/containers/containers.conf.d__.
+__\$XDG_CONFIG_HOME/containers/containers.conf.d/\*.conf__ files. When `$XDG_CONFIG_HOME` is not set it falls back to using `$HOME/.config` instead.
 Fields specified in a containers.conf file override the default options, as
 well as options in previously loaded containers.conf files.
--- a/SOURCES/default-policy.json
+++ b/SOURCES/default-policy.json
@ -8,16 +8,16 @@
        "docker": {
 	    "registry.access.redhat.com": [
 		{
-		    "type": "signedBy",
+		    "type": "sigstoreSigned",
-		    "keyType": "GPGKeys",
+		    "keyPath": "/etc/pki/sigstore/SIGSTORE-redhat-release3",
-		    "keyPaths": ["/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release", "/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta"]
+		    "rekorPublicKeyPath": "/etc/pki/sigstore/REKOR-signing-key"
 		}
 	    ],
 	    "registry.redhat.io": [
 		{
-		    "type": "signedBy",
+		    "type": "sigstoreSigned",
-		    "keyType": "GPGKeys",
+		    "keyPath": "/etc/pki/sigstore/SIGSTORE-redhat-release3",
-		    "keyPaths": ["/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release", "/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta"]
+		    "rekorPublicKeyPath": "/etc/pki/sigstore/REKOR-signing-key"
 		}
 	    ]
 	},
--- a/SOURCES/default.yaml
+++ b/SOURCES/default.yaml
--- a/gating.yaml
+++ b/gating.yaml
@ -0,0 +1,6 @@
 # recipients: jnovy, lsm5, santiago
 --- !Policy
 product_versions:
  - rhel-10
 decision_context: osci_compose_gate
 rules: []
--- a/SOURCES/mounts.conf
+++ b/SOURCES/mounts.conf
--- a/SOURCES/pyxis.sh
+++ b/SOURCES/pyxis.sh
--- a/SOURCES/registries.conf
+++ b/SOURCES/registries.conf
@ -18,9 +18,9 @@
 # of these registries, it should be added at the end of the list.
 #
 # # An array of host[:port] registries to try when pulling an unqualified image, in order.
-
+# unqualified-search-registries = ["example.com"]
 unqualified-search-registries = ["registry.access.redhat.com", "registry.redhat.io", "docker.io"]
-
+#
 # [[registry]]
 # # The "prefix" field is used to choose the relevant [[registry]] TOML table;
 # # (only) the TOML table with the longest match for the input image name
@ -46,11 +46,11 @@ unqualified-search-registries = ["registry.access.redhat.com", "registry.redhat.
 # #
 # # Example: Given
 # #   prefix = "example.com/foo"
-# #   location = "internal-registry-for-example.net/bar"
+# #   location = "internal-registry-for-example.com/bar"
 # # requests for the image example.com/foo/myimage:latest will actually work with the
-# # internal-registry-for-example.net/bar/myimage:latest image.
+# # internal-registry-for-example.com/bar/myimage:latest image.
 #
-# # The location can be empty iff prefix is in a
+# # The location can be empty if prefix is in a
 # # wildcarded format: "*.example.com". In this case, the input reference will
 # # be used as-is without any rewrite.
 # location = internal-registry-for-example.com/bar"
@ -74,6 +74,6 @@ unqualified-search-registries = ["registry.access.redhat.com", "registry.redhat.
 # # Given the above, a pull of example.com/foo/image:latest will try:
 # # 1. example-mirror-0.local/mirror-for-foo/image:latest
 # # 2. example-mirror-1.local/mirrors/foo/image:latest
-# # 3. internal-registry-for-example.net/bar/image:latest
+# # 3. internal-registry-for-example.com/bar/image:latest
 # # in order, and use the first one that exists.
-short-name-mode = "permissive"
+short-name-mode = "enforcing"
--- a/registry.access.redhat.com.yaml
+++ b/registry.access.redhat.com.yaml
@ -0,0 +1,3 @@
 docker:
     registry.access.redhat.com:
         use-sigstore-attachments: true
--- a/registry.redhat.io.yaml
+++ b/registry.redhat.io.yaml
@ -0,0 +1,3 @@
 docker:
     registry.redhat.io:
         use-sigstore-attachments: true
--- a/SOURCES/seccomp.json
+++ b/SOURCES/seccomp.json
@ -55,9 +55,16 @@
 		{
 			"names": [
 				"bdflush",
 				"cachestat",
 				"futex_requeue",
 				"futex_wait",
 				"futex_waitv",
 				"futex_wake",
 				"io_pgetevents",
 				"io_pgetevents_time64",
 				"kexec_file_load",
 				"kexec_load",
 				"map_shadow_stack",
 				"migrate_pages",
 				"move_pages",
 				"nfsservctl",
@ -72,9 +79,9 @@
 				"pciconfig_write",
 				"sgetmask",
 				"ssetmask",
 				"swapcontext",
 				"swapoff",
 				"swapon",
 				"syscall",
 				"sysfs",
 				"uselib",
 				"userfaultfd",
@ -149,6 +156,7 @@
 				"fchdir",
 				"fchmod",
 				"fchmodat",
 				"fchmodat2",
 				"fchown",
 				"fchown32",
 				"fchownat",
@ -316,7 +324,6 @@
 				"pwritev2",
 				"read",
 				"readahead",
 				"readdir",
 				"readlink",
 				"readlinkat",
 				"readv",
@ -404,15 +411,12 @@
 				"shmdt",
 				"shmget",
 				"shutdown",
 				"sigaction",
 				"sigaltstack",
 				"signal",
 				"signalfd",
 				"signalfd4",
 				"sigpending",
 				"sigprocmask",
 				"sigreturn",
 				"sigsuspend",
 				"socket",
 				"socketcall",
 				"socketpair",
@ -427,7 +431,6 @@
 				"sync",
 				"sync_file_range",
 				"syncfs",
 				"syscall",
 				"sysinfo",
 				"syslog",
 				"tee",
@ -440,7 +443,6 @@
 				"timer_gettime64",
 				"timer_settime",
 				"timer_settime64",
 				"timerfd",
 				"timerfd_create",
 				"timerfd_gettime",
 				"timerfd_gettime64",
@ -562,7 +564,8 @@
 		},
 		{
 			"names": [
-				"sync_file_range2"
+				"sync_file_range2",
 				"swapcontext"
 			],
 			"action": "SCMP_ACT_ALLOW",
 			"args": [],
@ -642,6 +645,20 @@
 			},
 			"excludes": {}
 		},
 		{
 			"names": [
 				"riscv_flush_icache"
 			],
 			"action": "SCMP_ACT_ALLOW",
 			"args": [],
 			"comment": "",
 			"includes": {
 				"arches": [
 					"riscv64"
 				]
 			},
 			"excludes": {}
 		},
 		{
 			"names": [
 				"open_by_handle_at"
@ -677,8 +694,8 @@
 				"bpf",
 				"fanotify_init",
 				"lookup_dcookie",
 				"perf_event_open",
 				"quotactl",
 				"quotactl_fd",
 				"setdomainname",
 				"sethostname",
 				"setns"
@ -695,11 +712,11 @@
 		},
 		{
 			"names": [
 				"bpf",
 				"fanotify_init",
 				"lookup_dcookie",
 				"perf_event_open",
 				"quotactl",
 				"quotactl_fd",
 				"setdomainname",
 				"sethostname",
 				"setns"
@ -1047,6 +1064,68 @@
 				]
 			},
 			"excludes": {}
 		},
 		{
 			"names": [
 				"bpf"
 			],
 			"action": "SCMP_ACT_ERRNO",
 			"args": [],
 			"comment": "",
 			"includes": {},
 			"excludes": {
 				"caps": [
 					"CAP_SYS_ADMIN",
 					"CAP_BPF"
 				]
 			},
 			"errnoRet": 1,
 			"errno": "EPERM"
 		},
 		{
 			"names": [
 				"bpf"
 			],
 			"action": "SCMP_ACT_ALLOW",
 			"args": [],
 			"comment": "",
 			"includes": {
 				"caps": [
 					"CAP_BPF"
 				]
 			},
 			"excludes": {}
 		},
 		{
 			"names": [
 				"perf_event_open"
 			],
 			"action": "SCMP_ACT_ERRNO",
 			"args": [],
 			"comment": "",
 			"includes": {},
 			"excludes": {
 				"caps": [
 					"CAP_SYS_ADMIN",
 					"CAP_BPF"
 				]
 			},
 			"errnoRet": 1,
 			"errno": "EPERM"
 		},
 		{
 			"names": [
 				"perf_event_open"
 			],
 			"action": "SCMP_ACT_ALLOW",
 			"args": [],
 			"comment": "",
 			"includes": {
 				"caps": [
 					"CAP_PERFMON"
 				]
 			},
 			"excludes": {}
 		}
 	]
 }
--- a/SOURCES/shortnames.conf
+++ b/SOURCES/shortnames.conf
@ -20,6 +20,7 @@
  "registry" = "docker.io/library/registry"
  "swarm" = "docker.io/library/swarm"
  # Fedora
  "fedora-bootc" = "registry.fedoraproject.org/fedora-bootc"
  "fedora-minimal" = "registry.fedoraproject.org/fedora-minimal"
  "fedora" = "registry.fedoraproject.org/fedora"
  # Gentoo
@ -37,6 +38,21 @@
  "leap-dnf" = "registry.opensuse.org/opensuse/leap-dnf"
  "leap-microdnf" = "registry.opensuse.org/opensuse/leap-microdnf"
  "tw-busybox" = "registry.opensuse.org/opensuse/busybox"
  # OTel (Open Telemetry) - opentelemetry.io
  "otel/autoinstrumentation-go" = "docker.io/otel/autoinstrumentation-go"
  "otel/autoinstrumentation-nodejs" = "docker.io/otel/autoinstrumentation-nodejs"
  "otel/autoinstrumentation-python" = "docker.io/otel/autoinstrumentation-python"
  "otel/autoinstrumentation-java" = "docker.io/otel/autoinstrumentation-java"
  "otel/autoinstrumentation-dotnet" = "docker.io/otel/autoinstrumentation-dotnet"
  "otel/opentelemetry-collector" = "docker.io/otel/opentelemetry-collector"
  "otel/opentelemetry-collector-contrib" = "docker.io/otel/opentelemetry-collector-contrib"
  "otel/opentelemetry-collector-contrib-dev" = "docker.io/otel/opentelemetry-collector-contrib-dev"
  "otel/opentelemetry-collector-k8s" = "docker.io/otel/opentelemetry-collector-k8s"
  "otel/opentelemetry-operator" = "docker.io/otel/opentelemetry-operator"
  "otel/opentelemetry-operator-bundle" = "docker.io/otel/opentelemetry-operator-bundle"
  "otel/operator-opamp-bridge" = "docker.io/otel/operator-opamp-bridge"
  "otel/semconvgen" = "docker.io/otel/semconvgen"
  "otel/weaver" = "docker.io/otel/weaver"
  # SUSE
  "suse/sle15" = "registry.suse.com/suse/sle15"
  "suse/sles12sp5" = "registry.suse.com/suse/sles12sp5"
@ -56,6 +72,7 @@
  "rhel7" = "registry.access.redhat.com/rhel7"
  "rhel7.9" = "registry.access.redhat.com/rhel7.9"
  "rhel-atomic" = "registry.access.redhat.com/rhel-atomic"
  "rhel9-bootc" = "registry.redhat.io/rhel9/rhel-bootc"
  "rhel-minimal" = "registry.access.redhat.com/rhel-minimal"
  "rhel-init" = "registry.access.redhat.com/rhel-init"
  "rhel7-atomic" = "registry.access.redhat.com/rhel7-atomic"
@ -100,7 +117,7 @@
  "ubi9/buildah" = "registry.access.redhat.com/ubi9/buildah"
  "ubi9/skopeo" = "registry.access.redhat.com/ubi9/skopeo"
  # Rocky Linux
-  "rockylinux" = "docker.io/library/rockylinux"
+  "rockylinux" = "quay.io/rockylinux/rockylinux"
  # Debian
  "debian" = "docker.io/library/debian"
  # Kali Linux
--- a/0
+++ b/0
--- a/storage.conf
+++ b/storage.conf
@ -0,0 +1,159 @@
 # This file is the configuration file for all tools
 # that use the containers/storage library. The storage.conf file
 # overrides all other storage.conf files. Container engines using the
 # container/storage library do not inherit fields from other storage.conf
 # files.
 #
 #  Note: The storage.conf file overrides other storage.conf files based on this precedence:
 #      /usr/containers/storage.conf
 #      /etc/containers/storage.conf
 #      $HOME/.config/containers/storage.conf
 #      $XDG_CONFIG_HOME/containers/storage.conf (if XDG_CONFIG_HOME is set)
 # See man 5 containers-storage.conf for more information
 # The "storage" table contains all of the server options.
 [storage]
 # Default storage driver, must be set for proper operation.
 driver = "overlay"
 # Temporary storage location
 runroot = "/run/containers/storage"
 # Priority list for the storage drivers that will be tested one
 # after the other to pick the storage driver if it is not defined.
 # driver_priority = ["overlay", "btrfs"]
 # Primary Read/Write location of container storage
 # When changing the graphroot location on an SELinux system, you must
 # ensure the labeling matches the default location's labels with the
 # following commands:
 # semanage fcontext -a -e /var/lib/containers/storage /NEWSTORAGEPATH
 # restorecon -R -v /NEWSTORAGEPATH
 graphroot = "/var/lib/containers/storage"
 # Optional alternate location of image store if a location separate from the
 # container store is required. If set, it must be different than graphroot.
 # imagestore = ""
 # Storage path for rootless users
 #
 # rootless_storage_path = "$HOME/.local/share/containers/storage"
 # Transient store mode makes all container metadata be saved in temporary storage
 # (i.e. runroot above). This is faster, but doesn't persist across reboots.
 # Additional garbage collection must also be performed at boot-time, so this
 # option should remain disabled in most configurations.
 # transient_store = true
 [storage.options]
 # Storage options to be passed to underlying storage drivers
 # AdditionalImageStores is used to pass paths to additional Read/Only image stores
 # Must be comma separated list.
 additionalimagestores = [
 ]
 # Options controlling how storage is populated when pulling images.
 [storage.options.pull_options]
 # Enable the "zstd:chunked" feature, which allows partial pulls, reusing
 # content that already exists on the system. This is disabled by default,
 # and must be explicitly enabled to be used. For more on zstd:chunked, see
 # https://github.com/containers/storage/blob/main/docs/containers-storage-zstd-chunked.md
 # This is a "string bool": "false" | "true" (cannot be native TOML boolean)
 # enable_partial_images = "false"
 # Tells containers/storage to use hard links rather then create new files in
 # the image, if an identical file already existed in storage.
 # This is a "string bool": "false" | "true" (cannot be native TOML boolean)
 # use_hard_links = "false"
 # Path to an ostree repository that might have
 # previously pulled content which can be used when attempting to avoid
 # pulling content from the container registry.
 # ostree_repos=""
 # If set to "true", containers/storage will convert images that are
 # not already in zstd:chunked format to that format before processing
 # in order to take advantage of local deduplication and hard linking.
 # It is an expensive operation so it is not enabled by default.
 # This is a "string bool": "false" | "true" (cannot be native TOML boolean)
 # convert_images = "false"
 # Root-auto-userns-user is a user name which can be used to look up one or more UID/GID
 # ranges in the /etc/subuid and /etc/subgid file.  These ranges will be partitioned
 # to containers configured to create automatically a user namespace.  Containers
 # configured to automatically create a user namespace can still overlap with containers
 # having an explicit mapping set.
 # This setting is ignored when running as rootless.
 # root-auto-userns-user = "storage"
 #
 # Auto-userns-min-size is the minimum size for a user namespace created automatically.
 # auto-userns-min-size=1024
 #
 # Auto-userns-max-size is the maximum size for a user namespace created automatically.
 # auto-userns-max-size=65536
 [storage.options.overlay]
 # ignore_chown_errors can be set to allow a non privileged user running with
 # a single UID within a user namespace to run containers. The user can pull
 # and use any image even those with multiple uids.  Note multiple UIDs will be
 # squashed down to the default uid in the container.  These images will have no
 # separation between the users in the container. Only supported for the overlay
 # and vfs drivers.
 # This is a "string bool": "false" | "true" (cannot be native TOML boolean)
 #ignore_chown_errors = "false"
 # Inodes is used to set a maximum inodes of the container image.
 # inodes = ""
 # Path to an helper program to use for mounting the file system instead of mounting it
 # directly.
 #mount_program = "/usr/bin/fuse-overlayfs"
 # mountopt specifies comma separated list of extra mount options
 mountopt = "nodev,metacopy=on"
 # Set to skip a PRIVATE bind mount on the storage home directory.
 # This is a "string bool": "false" | "true" (cannot be native TOML boolean)
 # skip_mount_home = "false"
 # Set to use composefs to mount data layers with overlay.
 # This is a "string bool": "false" | "true" (cannot be native TOML boolean)
 # use_composefs = "false"
 # Size is used to set a maximum size of the container image.
 # size = ""
 # ForceMask specifies the permissions mask that is used for new files and
 # directories.
 #
 # The values "shared" and "private" are accepted.
 # Octal permission masks are also accepted.
 #
 #  "": No value specified.
 #     All files/directories, get set with the permissions identified within the
 #     image.
 #  "private": it is equivalent to 0700.
 #     All files/directories get set with 0700 permissions.  The owner has rwx
 #     access to the files. No other users on the system can access the files.
 #     This setting could be used with networked based homedirs.
 #  "shared": it is equivalent to 0755.
 #     The owner has rwx access to the files and everyone else can read, access
 #     and execute them. This setting is useful for sharing containers storage
 #     with other users.  For instance have a storage owned by root but shared
 #     to rootless users as an additional store.
 #     NOTE:  All files within the image are made readable and executable by any
 #     user on the system. Even /etc/shadow within your image is now readable by
 #     any user.
 #
 #   OCTAL: Users can experiment with other OCTAL Permissions.
 #
 #  Note: The force_mask Flag is an experimental feature, it could change in the
 #  future.  When "force_mask" is set the original permission mask is stored in
 #  the "user.containers.override_stat" xattr and the "mount_program" option must
 #  be specified. Mount programs like "/usr/bin/fuse-overlayfs" present the
 #  extended attribute permissions to processes within containers rather than the
 #  "force_mask"  permissions.
 #
 # force_mask = ""
--- a/SOURCES/update-vendored.sh
+++ b/SOURCES/update-vendored.sh
@ -25,6 +25,9 @@ for P in podman skopeo buildah; do
  fi
  rm -rf *SPECPARTS
  DIR=`ls -d -- */ | grep "$P"`
  if [[ $DIR == *-build/ ]]; then
    DIR=`ls -d $DIR/* | grep -v SPECPARTS`
  fi
  grep github.com/containers/image $DIR/go.mod | cut -d\  -f2 | sed 's,-.*,,'>> /tmp/ver_image
  grep github.com/containers/common $DIR/go.mod | cut -d\  -f2 | sed 's,-.*,,' >> /tmp/ver_common
  grep github.com/containers/storage $DIR/go.mod | cut -d\  -f2 | sed 's,-.*,,' >> /tmp/ver_storage
--- a/SOURCES/update.sh
+++ b/SOURCES/update.sh
@ -30,10 +30,11 @@ for FILE in *; do
 done
 ensure storage.conf    driver                        \"overlay\"
 ensure storage.conf    mountopt                      \"nodev,metacopy=on\"
-if pwd | grep rhel-8 > /dev/null
+ensure registries.conf unqualified-search-registries [\"registry.access.redhat.com\",\ \"registry.redhat.io\",\ \"docker.io\"]
 if pwd | grep -e rhel-8 -e c8s > /dev/null
 then
 awk -i inplace '/#default_capabilities/,/#\]/{gsub("#","",$0)}1' containers.conf
 ensure registries.conf unqualified-search-registries [\"registry.access.redhat.com\",\ \"registry.redhat.io\",\ \"docker.io\"]
 ensure registries.conf short-name-mode               \"permissive\"
 ensure containers.conf runtime                       \"runc\"
 ensure containers.conf events_logger                 \"file\"
@ -49,19 +50,30 @@ then
  sed -i '/^default_capabilities/a \
  "SYS_CHROOT",' containers.conf
 fi
-else
+
-ensure registries.conf unqualified-search-registries [\"registry.access.redhat.com\",\ \"registry.redhat.io\",\ \"docker.io\"]
+elif pwd | grep -e rhel-9 -e c9s > /dev/null
 then
 ensure registries.conf short-name-mode               \"enforcing\"
 ensure containers.conf runtime                       \"crun\"
 elif pwd | grep -e rhel-10 -e c10s > /dev/null
 then
 ensure registries.conf short-name-mode               \"enforcing\"
 ensure containers.conf runtime                       \"crun\"
 ensure containers.conf log_driver                    \"k8s-file\"
 else
 echo "Unknown release"
 fi
 [ `grep \"keyctl\", seccomp.json | wc -l` == 0 ] && sed -i '/\"kill\",/i \
 				"keyctl",' seccomp.json
 [ `grep \"socket\", seccomp.json | wc -l` == 0 ] && sed -i '/\"socketcall\",/i \
 				"socket",' seccomp.json
 rhpkg clone redhat-release
 cd redhat-release
-rhpkg switch-branch rhel-9.4.0
+rhpkg switch-branch rhel-10.0
 rhpkg prep
-cp -f redhat-release-*/RPM-GPG* ../
+cp -f redhat-release-*/REKOR-signing-key ../
 cp -f redhat-release-*/SIGSTORE-redhat-release3 ../
 cd -
 rm -rf redhat-release