Merge pull request #965 from cgwalters/release

Release 1.1.3

Author: cgwalters

Cargo.lock

@@ -23,4 +23,4 @@ part of a build process; it will error if any problems are detected.
 
 # VERSION
 
-v1.1.0
+v1.1.3

docs/src/man/bootc-container-lint.md

@@ -30,4 +30,4 @@ bootc-container-help(8)
 
 # VERSION
 
-v1.1.0
+v1.1.3

docs/src/man/bootc-container.md

@@ -36,4 +36,4 @@ Only changes to the \`spec\` section are honored.
 
 # VERSION
 
-v1.1.0
+v1.1.3

docs/src/man/bootc-edit.md

@@ -0,0 +1,30 @@
+# NAME
+
+bootc-install-ensure-completion - Intended for use in environments that
+are performing an ostree-based installation, not bootc
+
+# SYNOPSIS
+
+**bootc install ensure-completion** \[**-h**\|**\--help**\]
+
+# DESCRIPTION
+
+Intended for use in environments that are performing an ostree-based
+installation, not bootc.
+
+In this scenario the installation may be missing bootc specific features
+such as kernel arguments, logically bound images and more. This command
+can be used to attempt to reconcile. At the current time, the only
+tested environment is Anaconda using \`ostreecontainer\` and it is
+recommended to avoid usage outside of that environment. Instead, ensure
+your code is using \`bootc install to-filesystem\` from the start.
+
+# OPTIONS
+
+**-h**, **\--help**
+
+:   Print help (see a summary with -h)
+
+# VERSION
+
+v1.1.3

docs/src/man/bootc-install-ensure-completion.md

@@ -27,4 +27,4 @@ string-valued filesystem name suitable for passing to \`mkfs.\$type\`.
 
 # VERSION
 
-v1.1.0
+v1.1.3

docs/src/man/bootc-install-print-configuration.md

@@ -10,8 +10,8 @@ bootc-install-to-disk - Install to the target block device
 \[**\--enforce-container-sigpolicy**\] \[**\--target-ostree-remote**\]
 \[**\--skip-fetch-check**\] \[**\--disable-selinux**\] \[**\--karg**\]
 \[**\--root-ssh-authorized-keys**\] \[**\--generic-image**\]
-\[**\--stateroot**\] \[**\--via-loopback**\] \[**-h**\|**\--help**\]
-\<*DEVICE*\>
+\[**\--bound-images**\] \[**\--stateroot**\] \[**\--via-loopback**\]
+\[**-h**\|**\--help**\] \<*DEVICE*\>
 
 # DESCRIPTION
 
@@ -130,6 +130,19 @@ boot.
 \- All bootloader types will be installed - Changes to the system
 firmware will be skipped
 
+**\--bound-images**=*BOUND_IMAGES* \[default: stored\]
+
+:   How should logically bound images be retrieved\
+
+\
+*Possible values:*
+
+> -   stored: Bound images must exist in the sources root container
+>     storage (default)
+>
+> -   pull: Bound images will be pulled and stored directly in the
+>     targets bootc container storage
+
 **\--stateroot**=*STATEROOT*
 
 :   The stateroot name to use. Defaults to \`default\`
@@ -149,4 +162,4 @@ firmware will be skipped
 
 # VERSION
 
-v1.1.0
+v1.1.3

docs/src/man/bootc-install-to-disk.md

@@ -10,8 +10,9 @@ bootc-install-to-existing-root - Install to the host root filesystem
 \[**\--target-ostree-remote**\] \[**\--skip-fetch-check**\]
 \[**\--disable-selinux**\] \[**\--karg**\]
 \[**\--root-ssh-authorized-keys**\] \[**\--generic-image**\]
-\[**\--stateroot**\] \[**\--acknowledge-destructive**\]
-\[**-h**\|**\--help**\] \[*ROOT_PATH*\]
+\[**\--bound-images**\] \[**\--stateroot**\]
+\[**\--acknowledge-destructive**\] \[**-h**\|**\--help**\]
+\[*ROOT_PATH*\]
 
 # DESCRIPTION
 
@@ -115,6 +116,19 @@ boot.
 \- All bootloader types will be installed - Changes to the system
 firmware will be skipped
 
+**\--bound-images**=*BOUND_IMAGES* \[default: stored\]
+
+:   How should logically bound images be retrieved\
+
+\
+*Possible values:*
+
+> -   stored: Bound images must exist in the sources root container
+>     storage (default)
+>
+> -   pull: Bound images will be pulled and stored directly in the
+>     targets bootc container storage
+
 **\--stateroot**=*STATEROOT*
 
 :   The stateroot name to use. Defaults to \`default\`
@@ -129,9 +143,10 @@ firmware will be skipped
 
 \[*ROOT_PATH*\] \[default: /target\]
 
-:   Path to the mounted root; its expected to invoke podman with \`-v
-    /:/target\`, then supplying this argument is unnecessary
+:   Path to the mounted root; this is now not necessary to provide.
+    Historically it was necessary to ensure the host rootfs was mounted
+    at here via e.g. \`-v /:/target\`
 
 # VERSION
 
-v1.1.0
+v1.1.3

docs/src/man/bootc-install-to-existing-root.md

@@ -13,7 +13,8 @@ filesystem structure
 \[**\--target-ostree-remote**\] \[**\--skip-fetch-check**\]
 \[**\--disable-selinux**\] \[**\--karg**\]
 \[**\--root-ssh-authorized-keys**\] \[**\--generic-image**\]
-\[**\--stateroot**\] \[**-h**\|**\--help**\] \<*ROOT_PATH*\>
+\[**\--bound-images**\] \[**\--stateroot**\] \[**-h**\|**\--help**\]
+\<*ROOT_PATH*\>
 
 # DESCRIPTION
 
@@ -144,6 +145,19 @@ boot.
 \- All bootloader types will be installed - Changes to the system
 firmware will be skipped
 
+**\--bound-images**=*BOUND_IMAGES* \[default: stored\]
+
+:   How should logically bound images be retrieved\
+
+\
+*Possible values:*
+
+> -   stored: Bound images must exist in the sources root container
+>     storage (default)
+>
+> -   pull: Bound images will be pulled and stored directly in the
+>     targets bootc container storage
+
 **\--stateroot**=*STATEROOT*
 
 :   The stateroot name to use. Defaults to \`default\`
@@ -161,4 +175,4 @@ mounting. To override this, use \`\--root-mount-spec\`.
 
 # VERSION
 
-v1.1.0
+v1.1.3

docs/src/man/bootc-install-to-filesystem.md

@@ -10,7 +10,7 @@ bootc-install - Install the running container to a target
 
 Install the running container to a target.
 
-\## Understanding installations
+## Understanding installations
 
 OCI containers are effectively layers of tarballs with JSON for
 metadata; they cannot be booted directly. The \`bootc install\` flow is
@@ -48,6 +48,11 @@ bootc-install-to-existing-root(8)
 
 :   Install to the host root filesystem
 
+bootc-install-ensure-completion(8)
+
+:   Intended for use in environments that are performing an ostree-based
+    installation, not bootc
+
 bootc-install-print-configuration(8)
 
 :   Output JSON to stdout that contains the merged installation
@@ -61,4 +66,4 @@ bootc-install-help(8)
 
 # VERSION
 
-v1.1.0
+v1.1.3