Add package persistence for image mode hosts

guides/common/assembly_package-mode-and-image-mode-hosts.adoc

@@ -10,6 +10,12 @@ include::modules/proc_viewing-booted-container-images-by-using-cli.adoc[leveloff
 
 include::modules/con_package-persistence-on-image-mode-hosts.adoc[leveloffset=+1]
 
-include::modules/proc_generating-a-containerfile-command-with-transient-packages.adoc[leveloffset=+1]
+include::modules/con_persisting-transient-packages-in-your-image.adoc[leveloffset=+1]
+
+include::modules/proc_generating-a-containerfile-command-by-using-web-ui.adoc[leveloffset=+2]
+
+include::modules/proc_generating-a-containerfile-command-by-using-cli.adoc[leveloffset=+2]
+
+include::modules/proc_generating-a-containerfile-command-by-using-api.adoc[leveloffset=+2]
 
 include::modules/ref_remote-execution-jobs-for-image-mode-hosts.adoc[leveloffset=+1]

guides/common/modules/con_package-persistence-on-image-mode-hosts.adoc

@@ -6,7 +6,8 @@
 [role="_abstract"]
 Any packages installed on an image mode host after the host is booted are transient and lost after a reboot.
 
-To persist packages on an image mode host, you can build a new container image that includes the necessary packages.
-After upgrading the image mode host to this image, the new packages are installed permanently on the host.
-
 You can view the persistence of installed packages on an image mode host by navigating to the host details in the {ProjectWebUI}, selecting *Content* > *Packages*, and checking the *Persistence* column.
+In Hammer CLI, you can view the persistence by running `hammer host package list --host-id _My_Host_ID_ --fields ALL`.
+
+To persist packages on an image mode host, you can build a new container image that includes the necessary packages.
+After upgrading the image mode host to the new image, the new packages are installed permanently on the host.

guides/common/modules/con_persisting-transient-packages-in-your-image.adoc

@@ -0,0 +1,8 @@
+:_mod-docs-content-type: CONCEPT
+
+[id="persisting-transient-packages-in-your-image"]
+= Persisting transient packages in your image
+
+[role="_abstract"]
+You can generate a Containerfile command with transient packages to install the packages in your container image.
+Then, you can use this command to rebuild your image to make the packages persistent.

guides/common/modules/proc_generating-a-containerfile-command-by-using-api.adoc

@@ -0,0 +1,17 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="generating-a-containerfile-command-by-using-api"]
+= Generating a Containerfile command by using {Project} API
+
+[role="_abstract"]
+You can generate a Containerfile command by using {Project} API to persist transient packages in your container image.
+
+.Prerequisites
+* Your {Project} account has a role that grants the `view_hosts` permission.
+
+.Procedure
+. Send a `GET` request to the `/api/hosts/:host_id/transient_packages/containerfile_install_command` endpoint.
+. Copy the generated command from the response.
+
+.Next steps
+* Include the generated command in your Containerfile and rebuild the image.

guides/common/modules/proc_generating-a-containerfile-command-by-using-cli.adoc

@@ -0,0 +1,22 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="generating-a-containerfile-command-by-using-cli"]
+= Generating a Containerfile command by using Hammer CLI
+
+[role="_abstract"]
+You can generate a Containerfile command by using Hammer CLI to persist transient packages in your container image.
+
+.Prerequisites
+* Your {Project} account has a role that grants the `view_hosts` permission.
+
+.Procedure
+. Generate the Containerfile command:
++
+[options="nowrap", subs="+quotes,attributes"]
+----
+$ hammer host package containerfile-install-command
+----
+. Copy the generated command from the output.
+
+.Next steps
+* Include the generated command in your Containerfile and rebuild the image.

guides/common/modules/proc_generating-a-containerfile-command-with-transient-packages.adoc → guides/common/modules/proc_generating-a-containerfile-command-by-using-web-ui.adoc

@@ -1,19 +1,17 @@
 :_mod-docs-content-type: PROCEDURE
 
-[id="generating-a-containerfile-command-with-transient-packages"]
-= Generating a Containerfile command with transient packages
+[id="generating-a-containerfile-command-by-using-web-ui"]
+= Generating a Containerfile command by using {ProjectWebUI}
 
 [role="_abstract"]
-You can generate a Containerfile command with transient packages to install the packages in your container image.
-Then, you can use this command to rebuild your image to make the packages persistent.
-This command is also available from Hammer CLI and {Project} API.
+You can generate a Containerfile command by using {ProjectWebUI} to persist transient packages in your container image.
 
 .Prerequisites
 * Your {Project} account has a role that grants the `view_hosts` permission.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Hosts* > *All Hosts*.
-. Select a host.
+. Click the name of a host.
 . Select the *Content* tab.
 . Select the *Packages* tab.
 . Select the packages you want to include in the command.
@@ -22,6 +20,5 @@ This command is also available from Hammer CLI and {Project} API.
 . If {Project} does not recognize persistence for any of the selected packages and you want to include them in the command, enable *Include packages with unknown persistence*.
 . Click *Copy* to copy the command to your clipboard.
 
-[role="_additional-resources"]
 .Next steps
-* Include this command in your Containerfile and rebuild the image.
+* Include the generated command in your Containerfile and rebuild the image.